((Today, of course, I would try again: more people have worked both on the tech itself and on making it accessible in the meantime. I'm hopeful modular implicits or something 1MLish works out, too.))
I don’t share the concern. I remember lots of similar concerns around things that were totally uncontroversial now; e.g. “none.” vs. “None”
-
-
Or capture clauses. This is actually a very similar situation to capture clauses, and it ended up not mattering at all.
-
That's because we have `move` for closures that capture. That's completely unrelated to reading code and not even knowing if a value was moved or not. I do know from my own experience that I rely on all those visual cues a lot. "none" vs "None" is entirely offtopic.
- 10 more replies
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.

