Interesting how ructc uses "ty" while scalac uses "tpe".
-
-
-
Embrace the backticks. We should use "`type`"!
2 replies 1 retweet 5 likes -
Replying to @propensive @dwijnand
why am I not surprised that this is coming from you
1 reply 0 retweets 3 likes -
Maybe because I've been saying for years, a) features exist so they can be used, and b) arbitrary choices (e.g. choice of abbreviation) are not intuitive, while taking the uniquely obvious option, even if it's slightly inconvenient, is.
2 replies 0 retweets 11 likes -
Replying to @propensive @larsr_h
How many times and across how many people are you willing to multiple that "slightly inconvenient" before you consider the alternative (teaching newcomers that "tpe" means "type") a better trade-off?
2 replies 0 retweets 2 likes -
The trade-off is on the learning curve, for the benefit of the uninitiated and to the detriment of the experienced. Everyone has the cost of learning that tpe = type, but only the subset who use it extensively feel the cost of typing the backticks.
4 replies 0 retweets 3 likes -
I will offer that by the time you encounter tpe its naming is the least of your problems.
1 reply 0 retweets 10 likes -
Yes, when you've come down to the optimization of renaming tpe to `type`, you're basically rearranging the deckchairs of method names on the Titanic of your codebase.
3 replies 0 retweets 5 likes -
Replying to @propensive @tpolecat and
I’m considering renaming a function to `match` next week.
1 reply 0 retweets 1 like
I'm still a little burned that no amount of backticking will allow you to name a method "notify".
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.