Voytek Pituła
Voytek Pituła
This feature is exactly what I would like to have. I'm creating lightweight tool for managing some data, but in the end this that have to be visualized. My tool...
I will jump in only as a user but bifunctor and stacktraces are two game changers I would like to have. And similar to @Avasil, in my usecases performance is...
Oh wow, that's pretty neat and it worked! One unfortunate consequence is that in practice my `bar` had multiple arguments and because of how type inference works, I had to...
Nope, only a single one but parameters become necessary because once I put `DefaultValueProvider[T]` in scope, type inference tries to use it everywhere where type param is not provided (infers...
Right! I haven't thought of that :) Thanks. You can keep this issue open if you'd like to improve the error message, otherwise, feel free to close.
> Would you expect the title to appear on the inside-side of the indicator, which would overlap parts of the active window? Yup, this sounds most intuitive. > Sigh. :-)...
Hey @virtualdvid, I'm not sure if thats gonna solve you problem but `scala-kernel` artifact is versioned with full scala version (e.g. `2.13.1` instead of `2.13`). You can see available artifacts...
@virtualdvid You're still trying to use `sh.almond#scala-kernel_2.12;0.9.1` whereas the correct one is `sh.almond#scala-kernel_2.12.10;0.9.1`. The easiest way to use it is: ``` libraryDependencies += "sh.almond" % "scala-kernel_2.12.10" % "0.9.1" ``` This...
I'm hitting the same problem right now, here is a fragment of `cs resolve -t sh.almond:scala-kernel_2.13.1:0.9.1`: ``` └─ sh.almond:scala-interpreter_2.13.1:0.9.1 ├─ com.lihaoyi:ammonite-repl_2.13.1:1.7.4 │ ├─ com.github.javaparser:javaparser-core:3.2.5 │ ├─ com.github.scopt:scopt_2.13:3.7.1 │ │ └─...