Imagining a language where non-empty collections are the default and you have to say Optional<String> to include empty string as a possible value. Many Collection APIs defined on Optional<T: Collection> wrapping those on T: Collection.
-
Show this thread
-
Replying to @UINT_MIN
And Nat does not include zero, so you can use Optional<Nat> instead
1 reply 0 retweets 7 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.