Jisoo Park
Jisoo Park
Unless the implicit parameter doesn't break a following method chain. I said a bit vaguely because I haven't tried it yet.
I'll look into it after first draft of new layout converter is done. If you really want to use `something_=` as well, here's a solution: ``` scala class ValueWithContext[A] private...
A brief confirmation in REPL: ``` scala scala> :paste // Entering paste mode (ctrl-D to finish) class C class V[A](val v: A, val c: C) object V { implicit def...
The error message in line 14 looks somewhat ugly though.
It makes sense. How about having `androidAPILevel` annotation with a SBT plugin which checks API compatibility according to the project's `minSdkVersion` at compile time?
Just a little possibility.. not sure of the implementation about automatic checking yet. But won't be the annotation visible in IDEs at least?
Also have an idea about the macro based re-implementation for class/helper generation which automatically wraps provided Android SDK in classpath, but it'll result in the lack of IDE support.
I agree. Then how about a macro shows a warning about using 'unsafe' listener in compile time?
It will be hard unless the scope is narrow enough. How about to show compile-time warning by default, and allow disabling it by importing specific value? Might need some time...
Using `lazy_dt` produces this error: ``` Error in rowSums(list(y = y, z = z)) : 'x' must be an array of at least two dimensions ```