| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
This is a gross hack to support the need for a $scope
binding when XML literals are created. It should go away
once we phase out XML literals. A library-based
solution should use implicits instead.
|
| | |
|
| |\
| |
| | |
Better positions for infix operations
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This has two advantages:
- We can distinguish BackquotedIdent from Ident, allowing the user to
use a defined "type `&`", see testcase.
- We get better positions for the operators. This is useful in IDEs, for
example to get the type at point.
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
To match the specs in
https://github.com/lampepfl/dotty/blob/master/docs/syntax-summary.txt
all occurences of Id, ident or Ident in comments have been replaced
with the terminal `id`.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
|
|
|
|
| |
Wildcards don't make sense as type arguments to methods, and I believe to keep things
simple this should also apply to method type arguments in patterns.
The best way to enforce this is to make use of the existing infrastructure in the parser
for topLevelTypes.
|
| |
|
|
|
| |
* Add error messages - Parsers.scala:712
* Tidy up imports and formatting
|
| |\
| |
| | |
Fix #1792: Allow newline in front of `{` for procedure syntax
|
| | | |
|
| |\ \
| | |
| | | |
Add implicit function types
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This will no longer be supported. On the other hand, as long as
the alternative is not yet legal in Scala2.x we cannot flag this
as an error. So the migration warning/error and patch code is
currently disabled.
|
| | | |
| | |
| | |
| | |
| | | |
- allow more than one implicit binding
- harmonize syntax in expressions and blocks
|
| | | |
| | |
| | |
| | |
| | | |
Implicit modifiers were quite irregular compared
to the other ones. This commit does a cleanup.
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| | |
Typer#ensureReported's comment outlines an example where errors
could go unreported, resulting in error trees after typer without
any reported error messages. This commit makes sure that at least
one error is reported if a tree node has an error type.
Fixes #1802.
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
| |
Some trees, which do not consume input have unassigned positions (so that
they can fit in whatever range they are integrated). It's therefore risky
to take the start or end of a parsed tree's position. This commit guards
against the case where the position of the tree does not exist.
|
| |
|
