TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Real Problems with Functional Languages

4 点作者 wingspan超过 4 年前

1 comment

rini17超过 4 年前
Often nulls and exceptions are used when the code isn't finished, or in general sense to deal with unknowns. Neither is well fit for this. I'd like instead to have "unknown" value/type which saves stack(or at least file/line) at time of its creation, but otherwise behaves like null/nothing. So that it can be easily ignored, but causes an exception when dereferencing is attempted. Having this additional creation-time stack information available in that exception should help debugging.