`None` or `Invalid` cases in enums are a bad idea · riki's house

hey! looks like you have JavaScript disabled.
I respect that decision, but you may find the experience of browsing the treehouse… not great.
for example, links to branches may not work properly. I cannot do anything about this; it's due to how the <details> element works.
(a <details> will not expand itself automatically to reveal the linked element to you.)
I did my best to at least keep the site readable in this state, but you can only do so much with plain HTML and CSS.

Pinky promise this website does not contain any malicious code such as trackers or cryptocurrency miners.
if you don't believe me, you're free to inspect the source yourself! all the scripts are written lovingly in vanilla JS (not minified!) by yours truly ❤️

and if this box is annoying, feel free to block it with uBlock Origin or something. I have no way of remembering you closed it, and don't wanna add a database to this website. simplicity rules!

by having them, you’re forcing your users into an API that forces them to think about the invalid case every time they read the value.
2023-10-11
- you’re repeating the million dollar mistake - null
  2023-10-11
- instead, use an explicit Option<T> or std::optional<T> or T? or … when you need to represent a possibly-invalid case
  2023-10-11