But you can’t name it “type”.
-
Not exactly, in my opinion. Everyone has the cost of learning _once_ that tpe = type, compared to everyone _always_ having the cost of typing the backticks (as well as teaching newcomers about backtick escaping.)
But I think there's a difference in the value of those two things which need to be learned: backtick-escaping is a language feature which is generally useful to know; a transferable skill. But tpe = type is arbitrary knowledge, which can't be reliably applied elsewhere.
-
-
I also feel like backticks look weird because they're unfamiliar. We avoid them because they're rare, and they stay rare because we avoid them. Sure, they're never going to be commonplace, but I sort of feel we shouldn't keep them artificially and disproportionately uncommon.
-
Also, look at us...
everything is so rosy in Scalaland this evening that our biggest complaint right now is tpe vs type! - Show replies
New conversation -
-
-
But it can! It's establishing a naming convention that I can adopt in my Scala code. And, provided it's not a keyword, in another language too (which is what I was exploring in my initial tweet). Scalameta actually has a document for all these.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.