wait you have to call some map() implementations as functions rather than methods? is there a rationale for this?
-
Show this thread
-
Replying to @mountain_ghosts
Basically types which act like pointers tend to have everything as functions, to avoid overlapping with the type the deref to
1 reply 0 retweets 1 like -
Replying to @sgrif
aaah, makes sense, because the . operator does deref magic
2 replies 0 retweets 0 likes
Replying to @mountain_ghosts
Yeah. It's not a decision I personally agree with, but the rationale is reasonable at least.
3:49 PM - 24 Mar 2019
0 replies
0 retweets
0 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.