| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
`typedFunction` uniformly recognizes Single Abstract Method types
and built-in `FunctionN` types, type checking literals regardless
of expected type.
`adapt` synthesizes an anonymous subclass of the SAM type, if
needed to meet the expected (non-`FunctionN`) type.
(Later, we may want to carry `Function` AST nodes with SAM types
through the whole pipeline until the back-end, and treat them
uniformly with built-in function types there too, emitting the
corresponding `invokedynamic` & `LambdaMetaFactory` bytecode.
Would be faster to avoid synthesizing all this code during type
checking...)
Refactor `typedFunction` for performance and clarity to avoid
non-local returns. A nice perk is that the error message for missing
argument types now indicates with `<error>` where they are missing
(see updated check file).
Allow pattern matching function literals when SAM type is expected
(SI-8429).
Support `return` in function body of SAM target type, by making the
synthetic `sam$body` method transparent to the `enclMethod` chain, so
that the `return` is interpreted in its original context.
A cleaner approach to inferring unknown type params of the SAM
method. Now that `synthesizeSAMFunction` operates on typed `Function`
nodes, we can take the types of the parameters and the body and
compare them against the function type that corresponds to the SAM
method's signature. Since we are reusing the typed body, we do need
to change owners for the symbols, and substitute the new method
argument symbols for the function's vparam syms.
Impl Notes:
- The shift from typing as a regular Function for SAM types was
triggered by limitation of the old approach, which deferred type
checking the body until it was in the synthetic SAM type
subclass, which would break if the expression was subsequently
retypechecked for implicit search. Other problems related to SAM
expansion in ctor args also are dodged now.
- Using `<:<`, not `=:=`, in comparing `pt`, as `=:=` causes
`NoInstance` exceptions when `WildcardType`s are encountered.
- Can't use method type subtyping: method arguments are in
invariant pos.
- Can't use STATIC yet, results in illegal bytecode. It would be a
better encoding, since the function body should not see members
of SAM class.
- This is all battle tested by running `synthesizeSAMFunction` on
all `Function` nodes while bootstrapping, including those where a
regular function type is expected. The only thing that didn't
work was regarding Function0 and the CBN transform, which breaks
outer path creation in lambdalift.
|
| |
|
|
|
|
|
|
|
|
| |
Initial work to change settings and test by Svyatoslav Ilinskiy
Thanks!
To avoid cycles during overload resolution (which showed up
during bootstrapping), and to improve performance, I've guarded
the detection of SAM types in `isCompatible` to cases when the
LHS is potentially compatible.
|
| |
|
|
|
|
|
|
|
| |
- Upgrade MathJax to 2.6. This fixes the vertical bar problem
on Chrome (https://github.com/mathjax/MathJax/issues/1300);
- Disambiguate link to Dynamic Selection;
- Consolidate type relations;
- Formatting, whitespace and linebreaks;
- SAM conversion.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
For each history entry, run the `Type`'s `toString` at the corresponding
phase, so that e.g., a method type's parameter symbols' `info`'s `toString`
runs at the phase corresponding to the type history we're turning into a
string.
|
| |
|
|
|
| |
It avoids confusion with existing test/partest scripts
that test the compiler in build/, while sbt it targeting build-sbt/.
|
| |\
| |
| | |
Fix scaladoc scroll and auto-expand on permalinks
|
| | |
| |
| |
| |
| |
| |
| | |
* Member description auto-expands
* If member comes from implicits is now becomes visible
* Member is no longer hidden by search bar after scrolling
* Permalink button now works when member is in a group (scrolling is still broken)
|
| |/ |
|
| |\
| |
| | |
Merge 2.11 to 2.12
|
| | |\ |
|
| | | |\
| | | |
| | | | |
Update IntelliJ build for use with sbt
|
| | | | | |
|
| | |\| | |
|
| | | |\ \
| | | | |
| | | | | |
SI-9488 - adds the same default toString format to Scala Futures as 2…
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Includes tests to verify the toString representations.
|
| | | |\ \ \
| | | |/ /
| | |/| | |
upgrade to latest scala-xml (namely 1.0.5)
|
| | | | |\ \ |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
there shouldn't be user-visible changes since 1.0.4, but regardless,
it's good to depend on the latest
|
| | | | | | | |
|
| | |\ \ \ \ \
| | | |_|_|/
| | |/| | | |
|
| | | |/ / / |
|
| | |\| | | |
|
| | | |\ \ \
| | | |_|/
| | |/| | |
bundle a newer Akka actors jar
|
| | | | |\ \
| | | |/ /
| | |/| | |
|
| | | | |/
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
might as well let people have the current stuff. I asked the
Akka folks and nobody saw a reason not to upgrade. this
version of Akka is the latest in the 2.3.x series, but is
also some months old, so no stability worries.
(this would have been included in 2.11.8 if I had thought of
it in time)
|
| |\ \ \ \
| | | | |
| | | | | |
Improve documentation of `GenSeqLike#length`
|
| | | | | |
| | | | |
| | | | |
| | | | | |
invocation of length method
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
SI-9314 Marginal edge case to warn-missing-interp
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Use the sym test on an expr that happens to be a subset of
idents and is not in scope. Other `${ operator_* }` warn.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
As an Easter egg, let "${} $x" forego the check on `x`.
In other words, empty expression interpolation looks too
degenerate to check.
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | | |
Edge cases of things not to warn about
include package names.
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Enable -YclasspathImpl:flat by default
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
:require was re-incarnated in https://github.com/scala/scala/pull/4051,
it seems to be used by the spark repl. This commit makes it work when
using the flat classpath representation.
|
| | | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Implements VirtualDirectoryFlatClassPath, which is required for the
presentation compiler created for the repl's tab-completion.
Various minor cleanups in the flat classpath implementation.
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Resolve several deprecation warnings
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Replace it with SyncVar#put
|
| | | | | | | |
|
| | | |/ / /
| |/| | |
| | | | |
| | | | | |
Explicitly annotate return type of trace macro to avoid type inference
|
| |\ \ \ \ \
| |_|/ / /
|/| | | | |
Organise Predef methods into Scaladoc groups
|
| | |/ / /
| | | |
| | | |
| | | |
| | | | |
By grouping members and providing descriptions the signal to noise
ratio in Predef is usefully enhanced.
|
| |\ \ \ \
| | | | |
| | | | | |
Fix some typos in `spec` documents and comments.
|
| | |/ / / |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
janekdb/topic/2.12.x-bump-sbt-compiler-interface-0.13.11
Update sbt version to most recent release
|
| | |/ / /
| | | |
| | | |
| | | | |
In preparation for removing Predef#error which was deprecated in 2.9.0.
|
| |\ \ \ \
| |/ / /
|/| | | |
New trait encoding using default methods
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The previous commit was used to build a interim release,
2.12.0-M3-dc9effe. That release process used dc9effe~1 as
STARR. (by passing the parameter STARR_REF to the bootstrap
job.)
This commit switches to using 2.12.0-M3-dc9effe as STARR.
It will not build until we have a public release of
scalacheck against 2.12.0-M3-dc9effe, as requested in
https://github.com/rickynils/scalacheck/issues/225
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
These manual mixins were forwarding to the impl classes have
just been removed. We can now rely on default methods instead.
Update Tests:
- Fix test/files/pos/t1237.scala, we can't have an outer field
in an interface, always use the outer method.
- Don't crash on meaningless trait early init fields
test/files/neg/t2796.scala
- Remove impl class relate parts of inner class test
- Remove impl class relate parts of elidable test
- Remove impl class related reflection test.
- Remove test solely about trait impl classes renaming
- Update check file with additional stub symbol error
- Disable unstable parts of serialization test.
- TODO explain, and reset the expectation
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Until now, concrete methods in traits were encoded with
"trait implementation classes".
- Such a trait would compile to two class files
- the trait interface, a Java interface, and
- the implementation class, containing "trait implementation methods"
- trait implementation methods are static methods has an explicit self
parameter.
- some methods don't require addition of an interface method, such as
private methods. Calls to these directly call the implementation method
- classes that mixin a trait install "trait forwarders", which implement
the abstract method in the interface by forwarding to the trait
implementation method.
The new encoding:
- no longer emits trait implementation classes or trait implementation
methods.
- instead, concrete methods are simply retained in the interface, as JVM 8
default interface methods (the JVM spec changes in
[JSR-335](http://download.oracle.com/otndocs/jcp/lambda-0_9_3-fr-eval-spec/index.html)
pave the way)
- use `invokespecial` to call private or particular super implementations
of a method (rather `invokestatic`)
- in cases when we `invokespecial` to a method in an indirect ancestor, we add
that ancestor redundantly as a direct parent. We are investigating alternatives
approaches here.
- we still emit trait fowrarders, although we are
[investigating](https://github.com/scala/scala-dev/issues/98) ways to only do
this when the JVM would be unable to resolve the correct method using its rules
for default method resolution.
Here's an example:
```
trait T {
println("T")
def m1 = m2
private def m2 = "m2"
}
trait U extends T {
println("T")
override def m1 = super[T].m1
}
class C extends U {
println("C")
def test = m1
}
```
The old and new encodings are displayed and diffed here: https://gist.github.com/retronym/f174d23f859f0e053580
Some notes in the implementation:
- No need to filter members from class decls at all in AddInterfaces
(although we do have to trigger side effecting info transformers)
- We can now emit an EnclosingMethod attribute for classes nested
in private trait methods
- Created a factory method for an AST shape that is used in
a number of places to symbolically bind to a particular
super method without needed to specify the qualifier of
the `Super` tree (which is too limiting, as it only allows
you to refer to direct parents.)
- I also found a similar tree shape created in Delambdafy,
that is better expressed with an existing tree creation
factory method, mkSuperInit.
|
