Scala
Scala is a general-purpose programming language providing support for functional programming and a strong static type system. Designed to be concise, many of Scala's design decisions aimed to address criticisms of Java.
Here are 10,521 public repositories matching this topic...
-
Updated
Nov 17, 2020 - Scala
-
Updated
Oct 14, 2020 - Scala
JDK
$ java --version
openjdk 15 2020-09-15
OpenJDK Runtime Environment (build 15+36-1562)
OpenJDK 64-Bit Server VM (build 15+36-1562, mixed mode, sharing)
-
Updated
Nov 3, 2020 - Scala
-
Updated
Oct 27, 2020 - TeX
Let's support at least reading "b3" header from a single string, most commonly traceid-spanid-1
It would also be nice to support optionally writing this, especially in message providers or others with constrained environments.
Expected behavior
As discussed on openzipkin/b3-propagation#21 and first implemented here: https://github.com/openzipkin/brave/blob/master/brave/src/main/java/bra
-
Updated
Nov 17, 2020 - Python
-
Updated
Nov 13, 2020 - Python
https://lichess.org/account/passwd gives no feedback in that case, aside from keeping the form fields filled in
there should be either some client side feedback, or added feedback for the server side validation
-
Updated
Nov 17, 2020 - Assembly
-
Updated
Oct 29, 2020 - Java
I run gatling.sh from a script. I encountered multiple occasions where Gatling failed, but the exit code was 0.
Expected behavior: exit code should be non-zero
Observed behavior: exit code 0
gatling.sh ....
at scala.App.main(App.scala:80)
at scala.App.main$(App.scala:78)
at io.gatling.compiler.ZincCompiler$.main(ZincCompiler.scala:40)
at io.gatli
Show[Throwable]
I just came across the fact that a Show[Throwable] exists.
- It is not wired up into
import Scalaz._, one needs toimport scalaz.std.java.throwable._ - It discards the stack trace entirely.
What's going on with this? :D
Is it OK if I fix both of these (for 7.2 and 7.3)?
steps
Global / onChangedBuildSource := ReloadOnSourceChangesproblem
It's developer specific preference, and we can't put it in global either because of datatype.
expectation
If there's a system property for this, we can use that as a default.
$ sbt -Dsbt.build.onchange=reload
$ sbt -Dsbt.build.onchange=warn
$ sbt -Dsbt.build.onchange=ignore
I just tried it out in Dotty for https://devblogs.microsoft.com/typescript/announcing-typescript-4-1-beta/#template-literal-types
➜ ~ dotr
Starting dotty REPL...
scala> type Color = "top" | "middle"
// defined alias type Color = "top" | "middle"
scala> def test(color:Color) = println(color)
def test(color: Color): Unit
scala> test("middle")
middle
scala> test("middel") This is a follow-up to #4097 where we used an AtomicInteger as a poor-mans replacement for a Semaphore with tryAcquire (or maybe even drainPermits).
Plotting UI revamp
The plotting UI leaves a lot to be desired:
- When you bring up the plotting UI, it's not obvious that you have to do some work to make a plot happen. If you don't, there's no error message, just a never-ending wait. (see https://gitter.im/polynote/polynote?at=5e0e36f9eac8d1511e9ed2ff )
- Why do we make you drag things onto axes? Especially when there is only one axis it could go onto (at leas
-
Updated
Nov 16, 2020 - Scala
-
Updated
Jul 27, 2020 - Python
-
Updated
Nov 8, 2020 - Kotlin
At this moment relu_layer op doesn't allow threshold configuration, and legacy RELU op allows that.
We should add configuration option to relu_layer.