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 11,079 public repositories matching this topic...
-
Updated
May 11, 2021 - Scala
-
Updated
Jan 9, 2021 - Scala
Are you looking for help?
No.
Play Version
2.6 to 2.8
API
Java / Scala
Expected Behavior
The instructions at https://www.playframework.com/documentation/2.8.x/Deploying-CloudFoundry work.
As it stands (see https://stackoverflow.com/a/62506207/4432837 and cloudfoundry/java-test-applications#20) those instructions are no longer applic
-
Updated
May 6, 2021 - Scala
It would be amazing to be able to flip the board for all the puzzles of a puzzle storm run. That would be a very efficient way to train the tactical vision from a defensive point of view.
-
Updated
Apr 12, 2021 - 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
May 9, 2021 - Python
-
Updated
May 7, 2021 - Python
-
Updated
May 10, 2021 - Assembly
-
Updated
Mar 30, 2021 - Java
It would be nice to pass multiple actions to a checkIf method , the same way as a check allows through the comma.
So, for example, instead of writing this:
.check(
checkIf("${first.exists()}")(do_first),
checkIf("$first.exists()}")(do_second),
checkIf("${first.exists()}")do_third)
it would be nice to have API as follows:
check(checkIf("${first.exists()}")(do
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)?
Minimized code
/** @define macro Super */
abstract class Super {
/** $macro */
def inherited: Int = 5
/** $macro */
def implemented: Unit
/** $macro */
def overridden: String = "test"
}
/**
* @define name default
* @define dummy dummy
*/
trait A[T] {
/** List $name */
def list(): List[T]
/** Gets the $name with the given $dummy */
def get(id:steps
I am using sbt 1.5.1 (with Coursier disabled) and I'm importing multiple libraries, e.g. a and b
a has a transitive dependency to c, version 1.1-prerelease
b has a transitive dependency to c, version 1.0
I am using early-semver as the version scheme.
problem
I'm getting an error when building that there are version conflicts that are suspected to be binary incompatible.
Adding a plain text to the header of a compiled and optimized .js-file may be useful for multiple reasons:
- Adding metadata like version, compiler settings, date, ...
- Adding execution information, e.g.
#!/usr/bin/env node - Adding a License, Author, Support info, URL, ...
Such a plain text header could easily be added to a .js in a postprocessing step after compilation. Howeve
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
Apr 21, 2021 - Scala
-
Updated
Mar 29, 2021 - Python
-
Updated
May 1, 2021 - Kotlin
-
Updated
May 10, 2021 - Emacs Lisp
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.