3 ms·

And here's the answer: https://github.com/rust-lang/rfcs/pull/2527#issuecomment-414635205 https://github.com/rust-lang/rfcs/pull/2527#issuecomment-414... WOW t

And here's the answer: https://github.com/rust-lang/rfcs/pull/2527#issuecomment-414635205 https://github.com/rust-lang/rfcs/pull/2527#issuecomment-414... WOW that's certainly a `wat` EDIT: ok - now that I look at it, I understand. My brain was very, very primed to see the <woe, is> as type parameters - and it's late

cies 6y ago
I'm not sure if this is were it came from, but "wat" reminds me of this short funny talk: https://www.destroyallsoftware.com/talks/wat https://www.destroyallsoftware.com/talks/wat Just some context.
- wffurr 6y ago
  https://knowyourmeme.com/memes/wat https://knowyourmeme.com/memes/wat
  - michael_j_ward 6y ago
    That page should have a link to that talk by Gary Bernhardt, because is the reason I reach for the term for "unexpected code behavior." And I'd wager that's true of many in the software community.
Sharlin 6y ago
To some extent the problem exists in all languages that overload the less than and greater than symbols to also mean angle brackets. C++ infamously has to disambiguate using either the `template` or `typename` keyword in some cases; Rust on the other hand uses the shorter `::` sigil but also more consistently so the programmer doesn’t have to guess or memorize complex rules. Java uses the rather awkward `object.<Type>method()` syntax when you need to explicitly specify a type parameter in a method invocation (which luckily is not very often, and to be fair does mirror the method declaration syntax so there’s that).