-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Error with type of <outer> when inlining from TASTY #3608
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
odersky
added a commit
to dotty-staging/dotty
that referenced
this issue
Dec 2, 2017
Tasty needs to know about outer selections as separate trees. So instead of exposing a name for outer selects we expose a tree format. This allows us to store the type of tree selection in the tree, which got lost before. Also: Change format of NAMEDarg to no longer require a length.
odersky
added a commit
to dotty-staging/dotty
that referenced
this issue
Dec 2, 2017
Tasty needs to know about outer selections as separate trees. So instead of exposing a name for outer selects we expose a tree format. This allows us to store the type of tree selection in the tree, which got lost before. Also: Change format of NAMEDarg to no longer require a length.
odersky
added a commit
to dotty-staging/dotty
that referenced
this issue
Dec 6, 2017
Tasty needs to know about outer selections as separate trees. So instead of exposing a name for outer selects we expose a tree format. This allows us to store the type of tree selection in the tree, which got lost before. Also: Change format of NAMEDarg to no longer require a length.
odersky
added a commit
to dotty-staging/dotty
that referenced
this issue
Dec 11, 2017
Tasty needs to know about outer selections as separate trees. So instead of exposing a name for outer selects we expose a tree format. This allows us to store the type of tree selection in the tree, which got lost before. Also: Change format of NAMEDarg to no longer require a length.
odersky
added a commit
to dotty-staging/dotty
that referenced
this issue
Dec 16, 2017
Tasty needs to know about outer selections as separate trees. So instead of exposing a name for outer selects we expose a tree format. This allows us to store the type of tree selection in the tree, which got lost before. Also: Change format of NAMEDarg to no longer require a length.
allanrenucci
added a commit
that referenced
this issue
Dec 18, 2017
Fix #3608: Treat outer selections as separate Tasty tree
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Fail to compile from TASTY
Can be reproduced with
The text was updated successfully, but these errors were encountered: