| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
avoid deprecated sbt 0.12 operators
|
| |
| |
| |
| | |
this is allowed in recent sbt versions
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
SI-10034: Regression: Make Future.failed(e).failed turn into a success instead of failure
|
| |/ |
|
|\ \
| |/
|/| |
Merge 2.11.x to 2.12.x [ci:last-only]
|
| |\ |
|
| | |\
| | | |
| | | | |
Silence SBT logging about macros and incremental compilation.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Since upgrading to SBT 0.13.12, clean builds have incurred warnings like:
Because JavaMirrors.scala contains a macro definition, the following
dependencies are invalidated unconditionally: ....
This commit disables this behaviour of the SBT incremental compiler in
the library and reflect projects, as these aren't regular macros (the
macro implementations are hard coded in the compiler in `FastTrack`)
so the new behaviour isn't actually improving correctness of inc.
compilation.
|
| |\| | |
|
| | |\ \
| | | | |
| | | | | |
[backport] Replace println with log calls in BrowsingLoaders
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This alternative symbol loader is used in the presentation compiler and
may generate output even when the compiler should be silent.
See SI-8717 for more context, even though this does not really
fix the ticket.
|
|/| | | |
| |/ / / |
|
| |\ \ \
| | |/ /
| |/| | |
SI-9913 Lead span iterator finishes at state -1
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Extra privacy, and the tricky state transition is made
more tabular.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Even if no elements fail the predicate (so that the trailing
iterator is empty).
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
No StackOverflowError in Java doc comment scanning
Fixes SI-10020 SI-10027
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Align the Scala and Java doc comment scanning methods a bit.
The Scala one especially had gotten a bit messy,
with regular block comments being kind of accumulated,
but never actually registered as DocComments.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Avoid StackOverflow on big comments.
Simplify `ScaladocJavaUnitScanner` while in there.
TODO: Do same for `ScaladocUnitScanner`?
|
|\ \ \ \ \
| | | | | |
| | | | | | |
fix starr version in README.md
|
|/ / / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Merge 2.12.0, starr=2.12.0, re-outsource scalacheck
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This reverts commit 22dac3118e97b2a4707d42ef1f47ac292a8ed385.
|
| | | | | | |
|
| |\ \ \ \ \ |
|
| | |\ \ \ \ \
| | | | | | | |
| | | | | | | | |
Bump to 2.12.0-RC2 starr and modules
|
| | |/ / / / / |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
It's propagated downstream by the '-main' build flows already
|
|\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
upgrade to sbt 0.13.13
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Binary version (for modules) is now 2.12,
starr is 2.12.0-RC2.
Also, drop repo_ref from jenkins.properties; It's
propagated downstream by the '-main' build flows already.
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
doc: minor grammatical fix
|
| | | | | | | | |
|
|\ \ \ \ \ \ \ \
| |/ / / / / / /
|/| | | | | | | |
doc: fix README link
|
|/ / / / / / / |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
upgrade to scala-xml 1.0.6
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
just because in general we want to ship the latest versions of the
modules, and some desirable-looking fixes went into 1.0.6
|
|\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | | |
SI-9909: corrected stream example so it does not give forward reference
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
error
|
|\ \ \ \ \ \ \ \ \
| |_|_|/ / / / / /
|/| | | | | | | | |
Frontend fixes for scala-dev#248
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Tighten some types (Symbol -> ClassSymbol / ModuleSymbol), use NonFatal
instead of catching Throwable.
Also don't run the classfile parser enteringPhase(phaseBeforeRefchecks)
anymore. This was added in 0ccdb15 but seems no longer required.
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
Skipping other annotations not only saves some cycles / GC, but also
prevents some spurious warnings / errors related to cyclic dependencies
when parsing annotation arguments refering to members of the class.
|
| | | | | | | | | |
|
| | | | | | | | | |
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
When unpickling a class, if the name and owner matches the current
`classRoot` of the unpickling Scan, that `classRoot` symbol is used
instead of creating a new symbol.
If, in addition, the class being unpickled has the MODULE flag, the
unpickler should use the `moduleRoot.moduleClass` symbol (instead of
creating a new one).
To identify the module class, the current implementation compares the
name and owner to the `classRoot`. This fails in case the `classRoot`
is `NoSymbol`, which can happen in corner cases (when a type alias
shadows a class symbol, scala-dev#248).
In this patch we identify the module class by comparing the name and
owner to the `moduleRoot` symbol directly (using a `toTypeName`).
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
In SymbolLoaders, when seeing a classfile `Foo.class`, we always
(unconditionally) create 3 symbols: a class, a module and a module
class. Some symbols get invalidated later (`.exists`).
Until now, the classfile parser (and unpickler) received the "root"
symbol as argument, which is the symbol whose type is being completed.
This is either the class symbol or the module symbol.
The classfile parser would then try to lookup the other symbol through
`root.companionClass` or `root.companionModule`. Howver, this lookup can
fail. One example is scala-dev#248: when a type alias (in a package
object) shadows a class symbol, `companionClass` will fail.
The implementations of the classfile parser / unpickler assume that
both the `clazz` and the `staticModule` symbols are available. This
change makes sure that they are always passed in explicitly.
Before this patch, in the example of scala-dev#248, the `classRoot` of
the unpickler was NoSymbol. This caused a bug when unpickling the
module class symbol, causing a second module class symbol to be created
mistakingly. The next commit cleans up this logic, more details there.
This second symbol would then cause the crash in the backend because it
doesn't have an `associatedFile`, therefore `isCoDefinedWith` would
spuriously return `true`.
|