A Scala annotation to add to return value to show that they are @important and ignoring them is likely a bug?
-
-
-
Replying to @viktorklang
@viktorklang@tpolecat "If you liked it, then you should have put a type on it."1 reply 0 retweets 1 like -
Replying to @gclaramunt
@gclaramunt@tpolecat if u liked it u shoulda put an@important on it ;-)1 reply 0 retweets 1 like -
Replying to @viktorklang
@viktorklang@gclaramunt confusion. We already have a way to say the return value is important ... you give it a type other than Unit.2 replies 0 retweets 15 likes -
Replying to @tpolecat
@tpolecat@viktorklang@gclaramunt Interesting. Though I sometime return a type which is fine to discard, e.g. a file copy summary.1 reply 0 retweets 0 likes -
Replying to @propensive
@propensive@tpolecat@viktorklang@gclaramunt what, you mean not everyone compiles with -Ywarn-value-discard and -Xfatal-warnings ?1 reply 0 retweets 1 like -
Replying to @NicolasRinaudo
@NicolasRinaudo@tpolecat@viktorklang@gclaramunt Some of us have unavoidable, spurious warnings... :(1 reply 0 retweets 1 like -
Replying to @propensive
@propensive@tpolecat@viktorklang@gclaramunt java interop, or are there "proper" scala scenarios where this might happen?1 reply 0 retweets 0 likes
@NicolasRinaudo @tpolecat @viktorklang @gclaramunt I get spurious warnings about dead code and usage of $s in @implicitNotFound annotations.
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.