this post was submitted on 05 Sep 2024
55 points (93.7% liked)
Programming
17436 readers
298 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
"Monadic type" has something like three meanings depending on context, and it's not clear which one you mean. One of them is common in math, but not so common in programming, so probably not that. But neither "parametric types with a single argument" nor "types that encode a category-theoretic monad" have the property you say, as far as I know.
I imagine you're probably referring to the latter, since the optional monad exists. That's very different from returning null. The inhabitants of
Integer
in Java, for example, are the boxed machine ints andnull
. The inhabitants ofOptional[Integer]
(it won't let me use angle brackets here) areOptional.of(i)
for each machine inti
,Optional.empty()
, andnull
.Optional.empty()
is not null and should not be called a "Null object." It's also not of typeInteger
, so you're not even allowed to return it unless the function type explicitly says so. Writing such function types is pretty uncommon to do in java programs but it's more normal in kotlin. In languages like Haskell, which don't havenull
at all, this is idiomatic.I think you're trying too hard to confuse yourself.