this post was submitted on 08 Dec 2023
622 points (96.4% liked)
Programmer Humor
32050 readers
1384 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Not quite, because the Maybe enum is neither int nor null, but it's own, third thing. So before you can do any operations with the return value, you need to handle both cases that could occur
Isn't that also true with compile-time type checking though? Eg. 0 + x where x is int|null would be detected? I don't have much experience here so I could be wrong but I can't think of a case where they're not equivalent
Most languages that let you do ambiguous return types don't do compile-time type checking, and vice versa. But if it's actually implemented that way, then it's logically equivalent, you're right. Still, I prefer having things explicit
Yeah it's nice to be able to see it
Yes it is