Furthermore, naming a class instance klass or clazz or claas is just an egregious abuse of English. What was ever wrong with cls?
-
-
Replying to @propensive
@propensive Somebody needs to make up a fancy Greek name for this kind of keyword-avoidance metaplasm.1 reply 0 retweets 0 likes -
Replying to @travisbrown
@travisbrown Yes - though I generally use the name I want in backticks. There's only one rule to remember then...1 reply 0 retweets 0 likes -
Replying to @propensive
@propensive I agree, but e.g. "clazz" is common practice, and a name for the practice would be descriptively useful in some situations.2 replies 0 retweets 0 likes -
Replying to @travisbrown
@travisbrown Agreed, clazz is the usual, though I've just seen clazz, claas and klass in the same project. So, obviously, I've used cls.1 reply 0 retweets 0 likes -
Replying to @propensive
@propensive@travisbrown the real problem is getting Class instances in the first place :) reflection only leads to eventual insanity!3 replies 1 retweet 0 likes -
Replying to @copumpkin
@copumpkin@propensive It even infects the (relatively innocent) compile-time kind—writing ".tpe" in#scala macros always hurts me a little.1 reply 0 retweets 0 likes
@travisbrown That's a more bearable abbreviation, though I know what you mean. And consequently tpe spreads into longer method names too...
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.