| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Names with internal $'s are entered in package scopes only if
- we look for a name with internal $'s.
- we want to know all the members of a package scope
This optimization seems to be fairly effective. The typical range
of package scopes that need $-names is between 0 and 20%. The optimization
seems to improve execution time of all unit tests by about 3%.
Also. drop the inheritance from Iterable to Scope. The reason
is that we now need a context parameter for toList and
other Iterable operations which makes them impossible to
fit into the Iterable framework.
|
|
|
|
|
| |
and generalize MethodParam to ParamRef, and
TypeParamInfo to ParamInfo
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Flags like Trait are in fact not always defined when a symbol
is created. For symbols loaded from class files, this flag, and
some other is defined only once the classfile has been loaded.
But this happens in general before the symbol is completed.
We model this distinction by separating from the `FromStartFlags` set
a new set `AfterLoadFlags` and distinguishing between the two sets
in `SymDenotations#is`.
Test case is enum-Option.scala. This erroneously complained before
that `Enum` was not a trait.
|
| |
|
| |
|
|
|
|
|
|
|
| |
* Fix varargs in methods (Issue: #1625)
* Fix minor comments
* Change varargs parameter message
* Fix failed test, fix case for constructor
|
|
|
|
|
|
|
|
|
| |
As part of https://github.com/lampepfl/dotty/issues/1589, use the
new error message for static super references where the qualifier
isn't a parent of the class.
Tested:
Added unit test.
|
|\
| |
| | |
Change "recursive/cyclic definitions needs type" errors to Message
|
| |
| |
| |
| | |
Fall-back to reporting "overloaded or recursive needs type".
|
| |
| |
| |
| |
| |
| | |
Split error messages for recursive method and overloaded method needs type into two (but
did not solve the analysis which to show).
Make CyclicReference type error construct corresponding error message.
|
| | |
|
| |\
| | |
| | |
| | | |
ennru_RecursiveNeedsType
|
| | | |
|
| |/
|/|
| |
| |
| | |
(1) Drop unused error message
(2) Drop test which is now illegal
|
|\ \
| | |
| | | |
Last changes before presentation at Matsuri
|
| |/ |
|
|/ |
|
|\
| |
| | |
Change 'is abstract; cannot be instantiated' to Message
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Fix off-by-one error in forward reference checking
|
| | | |
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| | |
Inlining is only well-defined if the body to inline does not
have any errors. We therefore check for errors before we
perform any transformation of trees related to inlining.
The error check is global, i.e. we stop on any error
not just on errors in the code to be inlined. This is a safe
approximation, of course.
|
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* Change 'forward reference extending over the definition' to Message
* Change 'forward reference extending over the definition' to Message
* pesky file should not be included
* Change 'forward reference extending over the definition' to Message (test case)
|
|
|
|
|
|
| |
* Change 'overrides nothing' to report via Message, split into two different messages
* Change 'overrides nothing' to report via Message, split into two different messages
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The following examples trigger the error message:
val x: Foo.this = ???
// Also triggers the error:
import foo.this
// Additionally, also slays the compiler
type X = Foo.this.type
|
| |
|
|
|
|
|
| |
* Add error messages - Parsers.scala:712
* Tidy up imports and formatting
|
|
|
|
|
|
| |
"Wrong number of args" only works for type arguments but was called also for
term arguments. Ideally we should have a WrongNumberOfArgs message that works for
both, but this will take some refactoring.
|
|
|
|
| |
559e49317912ce52c51e295346cebcafbb69462d)
|
| |
|
|
|
|
|
| |
Drop explicit types for local implicit vals of type Context
and Position. Exercises the functionality and shortens the code.
|
|
|
|
|
| |
Error messages of nested implicit failures are now
reported with the top-level message if -explaintypes is set.
|
|
|