| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
This allows to remove the ugly workaround for default methods.
There is also a slight adaptation for the new way to encode a
reference to the JS global scope in the IR.
|
| |
|
|
|
|
|
| |
This guarantees that we can bootstrap dotty without depending on
the binaries of scalajs-ir compiled by another Scala compiler.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Scala.js back-end can be enabled with the `-scalajs`
command-line option. Currently, it adds one phase to the pipeline,
which emits .sjsir files from trees.
A sandbox project `sjsSandbox`, in `sandbox/scalajs/`, can be used
to easily test Scala.js compilation. One can run the `main()`
method of the `hello.world` object with
> sjsSandbox/run
The back-end only contains the bare mimimum to compile the hello
world application in the sandbox. Anything else will blow up
(for example, primitive method calls). It is a work-in-progress.
|
|
|
|
|
|
|
|
| |
This should be safe now that run tests do not take so much memory
anymore (cf #1033 and #1076).
It would be even better if we could figure out why we're using so much
memory, but that's less important than avoiding spurious test failures.
|
| |
|
|\
| |
| | |
Add a `dotty-interfaces` package
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We introduce a new entry point for the compiler in
`dotty.tools.dotc.Driver`:
```
def process(args: Array[String], simple: interfaces.SimpleReporter,
callback: interfaces.CompilerCallback): interfaces.ReporterResult
```
Except for `args` which is just an array, the argument types and return
type of this method are Java interfaces defined in a new package called
`dotty-interfaces` which has a stable ABI. This means that you can
programmatically run a compiler with a custom reporter and callbacks
without having to recompile it against every version of dotty: you only
need to have `dotty-interfaces` present at compile-time and call the
`process` method using Java reflection.
See `test/test/InterfaceEntryPointTest.scala` for a concrete example.
This design is based on discussions with the IntelliJ IDEA Scala plugin
team. Thanks to Nikolay Tropin for the discussions and his PR
proposal (see #1011).
|
|/
|
|
|
|
|
|
|
| |
Upgrading sbt will allow us to experiment with bootstrapping
using sbt since 0.13.11 is the first release that supports building
with dotty (see https://github.com/smarter/dotty-bridge).
Upgrading scalastyle-sbt-plugin allows us to remove the workaround for
https://github.com/scalastyle/scalastyle/issues/156
|
|
|
|
|
|
|
|
|
|
|
|
| |
Settings `in Global` are moved to Build.settings. Otherwise they
are added *twice* in every project.
Project definitions use the `project` macro rather than the
`Project()` factory, as is the customary notation since sbt
0.13. The `Defaults.coreDefaultSettings` is therefore dropped.
The coding style of project definitions is adapted to the style
shown in sbt documentations.
|
|
|
|
| |
First step in fixing #1034
|
|
|
|
|
|
|
|
| |
We're getting a lot of OutOfMemoryException when the maximum size is 1
GB, but we cannot increase it too much without using up all the memory
available on the Jenkins instances, let's see if 1.1 GB is enough.
Also stop using a custom -Xss, the default of 1 MB should be good enough.
|
|
|
|
|
|
| |
Needs to go in before
https://github.com/scala/scala-jenkins-infra/pull/152
is deployed
|
|
|
|
|
| |
-language:_ does not work when compiling dotty with dotty because it
implies -language:keepUnions which prevents dotty from typechecking
|
|
|
|
|
|
|
| |
This is used by sbt to get the compiler's version.
The code to generate the resource comes from
http://www.scala-sbt.org/0.13/docs/Howto-Generating-Files.html#Generate+resources
|
|
|
|
|
|
| |
artifactory"
This reverts commit 2f41c73ee86a56b190758baaf5999ed85d2f57a1.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Ycheck that methods defined in ClassInfo exist in tree.
|
| |
| |
| |
| |
| |
| | |
Includes fix to emission of invokeDynamic instructions
in positions where expected type isn't the type of lambda being returned.
SI-9387
|
| |
| |
| |
| | |
Fixes bugs in handling try-finally blocks.
|
|/
|
|
|
| |
Done by setting an environment variable and checking it in runtime.
This enables Ycheck:all for all kinds of tests, including partest.
|
|
|
|
| |
More magic is needed, as enumerating array symbols does not work in backend.
|
|
|
|
| |
To make sure that artifact is the same.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
dotc: Get versions of all dependencies from Build.scala
|
| | |
|
|/
|
|
| |
Includes fixes to lambas, and no type projections in signatures.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This update allows to have non-static lambdas.
It doesn't mean that we should emit such,
as they are potential memory leak. See #480
Fixes #470
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Includes fixed for emitting string concatenation if string originates from an array.
Eg `"hello " + Array("world")(0)`
|
|
|
|
|
|
|
|
|
|
| |
Dotty requires a mangled bootclasspath to start.
It means that `console` mode of sbt doesn't work for us.
At least I wasn't able to make sbt fork in console,
so instead I've added a Scala-repl into dotty itself :-)
It would be good to make it use dotty one day when we have
a backend :-)
|