Besides, APIs shouldn't describe what's going on internally.
-
-
Using `catch` for opposite-ish things reminds me of `static` in C and the confusing nature of addr-of and by-ref syntax both using & even when they mean opposite things.
2 replies 0 retweets 0 likes -
It has a similar problem imo as the two uses of `unsafe`. I think we can do better than `catches`. Do we not like `throws` because it gives the wrong idea to Java programmers?
2 replies 0 retweets 1 like -
Exactly yeah. I think it gives the right idea, really. Though I guess making folks think we're like <other language that is different> might lead them to assume more than they should.
1 reply 0 retweets 0 likes -
I think it would be fine to tell new developers "it's like an exception but it only bubbles with `?`" A little later: "Also if you don't use `?` you can get your hands on the Result"
2 replies 0 retweets 1 like -
Replying to @wycats @ManishEarth and
That explanation kinda sounds too magical to me, vs. teaching the types - there's nothing special about the type besides the ? (and soon throws/catches/w.e) sugar and it being standard, and leading users to understand the types seems better?
2 replies 0 retweets 1 like -
Replying to @homomculus @wycats and
(Not that I particularly have a say in the process, just adding my 2¢ because something felt off to me about that post.)
1 reply 0 retweets 1 like -
Replying to @homomculus @wycats and
(everyone has a say, though if you want to seriously propose something commenting on the forum works best)
1 reply 0 retweets 1 like -
Replying to @ManishEarth
Yeah, it's more of like, I don't have the energy to respond to a discussion that built around a suggestion if I made one more "formally" via the forum or the like.
1 reply 0 retweets 0 likes -
Replying to @homomculus @ManishEarth
(vs. an informal comment dropped into a twitter thread that's already discussing details where it's not particularly unusual to just drop a response and then disengage)
2 replies 0 retweets 1 like
fwiw I love getting feedback on Twitter.
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.