| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Previous fix to value classes uncovered some questionable cases in the backend where result types of constructor signatures are surprising. It's not a big deal because these types will be ignored afterwards anyway. But
the method uncovered some questionable situations which we should follow up on. However, breaking 2.9 code because of this is way too harsh. That's why the asserts were converted to warnings.
review by @paulp, @adriaanm
|
|\
| |
| | |
Disabled generation of _1, _2, etc. methods.
|
| |
| |
| |
| |
| |
| |
| | |
This was part of the introduction of ProductN, which had
to go back into pandora's box because of issues with cycles
during typing. These should have been reverted along
with it.
|
|\ \
| | |
| | | |
SI-6526 Tail call elimination should descend deeper.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
It wasn't traversing into Select nodes nor into the receiver of
a tail call.
|
|\ \ \
| |_|/
|/| | |
Fix SI-6552, regression with self types.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
In 6eb55d4b7a we put in a remedy for an old issue SI-4560 which
had accumulated a number of sketchy partial remedies which carried
no tests to illustrate their necessity. Looks like at least one of
those was doing something useful. Here's to reversion-reversion.
This reverts commit c8bdf199, which itself reverted cb4fd6582.
|
|\ \
| | |
| | | |
Fix for SI-6537, inaccurate unchecked warning.
|
| |/
| |
| |
| |
| |
| |
| |
| | |
I found a more direct expression of the unchecked logic,
which should be much easier for others to verify. But the
bug being fixed here is that the unchecked checking happens
too early, and the sealed children of a symbol are not yet
visible if it is being simultaneously compiled.
|
|\ \
| | |
| | | |
avoid single-arg assert where harmful in duration-tck
|
| |/ |
|
|\ \
| | |
| | | |
Fixes SI-6170: issue with dragging scaladoc splitter over central iframe
|
| | | |
|
|\ \ \
| |_|/
|/| | |
Changes Tree and Type members from vals to defs.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Explanatory email:
The reflection API defines a great many abstract vals. I would
like these all to be defs. I'm sending a pull request to that end.
Reasons: for starters, they should default to being defs. It's a
decision to use vals for which one should have to supply reasons.
The reason for THAT is that defs can be implemented with vals, but
not vice versa.
Why does this matter? I can't find my long writing on the subject
of TypeRef. In short, we waste a huge amount of memory on its
fields, because given the way TypeRef is defined, each one demands
a pre, a sym, and an args. Except that somewhere between 1/3 and
1/2 have prefix "NoPrefix", and somewhere between 1/3 and 1/2 have
args "Nil". We know it at creation time, but we give every typeref
the whole field anyway.
At present there's no way to fix this which has acceptable
performance - i.e. custom subclasses save us lots of memory, but
are too much slower for having to use an extractor - but there's
no reason we should have to choose, and I fully expect to fix it
eventually. Let's not make that fix into a breaking change by
abstractly defining "pre" and "args" as field-requiring vals.
|
|\ \
| | |
| | | |
Pullrequest/reflection docs
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Additionally includes improvements, formatting fixes, and link
additions and fixes.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
blocked by SI-6511
|
| | |
| | |
| | |
| | | |
and warning cleanup
|
| | | |
|
| | |
| | |
| | |
| | | |
Oh those pretty groups, u gotta luv'em...
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
|/| | |
SI-6453 Documentation links for @switch are broken
|
| | | |
|
|\ \ \
| | | |
| | | | |
Scaladoc bugfixes for reflection
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
members
|
| | | | |
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
Fixed SI-6505. Respond to ask calls by immediate failure after compiler shutdown.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
shutdown.
When the compiler is asked to shutdown, it may still have items on the working queue, and more can be added by clients in other thread that don't *know* the compiler is down yet. These requests were never serviced, leading to deadlocks or timeouts.
review by @odersky, @hubertp
|
|\ \ \ \
| | | | |
| | | | | |
Fix for SI-6499, regression in type inference.
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I can't do any better than a reproduced comment:
For some reason which is still a bit fuzzy, we must let Nothing
through as a lower bound despite the fact that Nothing is always
a lower bound. My current supposition is that the side-effecting
type constraint accumulation mechanism depends on these subtype
tests being performed to make forward progress when there are
mutally recursive type vars. See pos/t6367 and pos/t6499 for the
competing test cases.
|
|\ \ \ \
| |_|/ /
|/| | | |
SI-6099 - Scaladoc for scala.concurrent incomplete
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is a rebase and resubmission of @phaller's pull
https://github.com/scala/scala/pull/1485
With the reviewers' comments additionally addressed
|
|\ \ \ \
| |/ / /
|/| | | |
Deprecated instrumentation API
|