wait you have to call some map() implementations as functions rather than methods? is there a rationale for this?
Basically types which act like pointers tend to have everything as functions, to avoid overlapping with the type the deref to
-
-
aaah, makes sense, because the . operator does deref magic
-
Yeah. It's not a decision I personally agree with, but the rationale is reasonable at least.
End of conversation
New conversation -
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.