Yeah, for this reason null shouldn’t be part of any production code. If there’s the possibility of having a null value, you need to check every variable or returned value to be safe.

These monads tell the consumer of your functions to do something (a check for emptiness or wait for it to be ready, or iterate it) to access the value inside. In a safe language, if the value is not wrapped by a monad, then you should expect to access it without issues.

I kind of get why people don’t want to call them monads, since it sounds like a heavy term and more things to learn that are not strictly “necessary”, but the earlier you learn about their importance, the earlier you can use any of their benefits in your codebase.

I am with you. To me these are non-obvious details, just a bug waiting to silently happen in production.

Pixel + Graphene OS is such a good combination! I’ve been using it for months now and I feel free with it.

I wish small pixels were still a thing, now they are all 6inch+

I would really consider to get a fairphone if they had a smaller variant. Lately I’ve grown tired of only having huge phones and I don’t mind making some hardware sacrifices if I can use it comfortably.

The Asus Zenfone 10 was a good candidate, but their bootloader unlocking tool is still down, so you may be locked to only 2 years of OS updates

If it is a pure value, I’d assume yes, but if it is tied to a side effect (E.g. write its value to a file), then it would be not used but still could break your app if removed.

I’m not familiar with rust language specifically, but generally that’s what could happen

I hope you have fun! You can ask anytime for help, it’s a great learning opportunity