miniblog.

Language design question: what type should `while True {}` have? Bottom: It doesn't contain any `break` statements. Unit: Treat loops with/without `break` consistently. I already have lints that warn on unreachable code after diverging loops, so the Unit case feels surprising.

It's odd how lazy evaluation is generally seen as a niche design choice, yet the vast majority of languages treat `foo() || bar()` as short-circuiting.

Are there any package managers that treat changelogs as a first class concept? I end up looking for a CHANGELOG.md or a CHANGES.txt in the source code repository every time. The lack of standard prevents package hosting services being able to show changes.