-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
document that Packages can be nested in <empty> package #13520
Comments
This isn't specific to TASTy, and I'm not sure if it's a bug or not. @odersky, wdty? I looked at this in #13113 where I left some notes. Also, @som-snytt's spent time on this, see also his #7891 and #13114. |
I think it's a bug. Will take a look. |
I think the change, or at least the start of the change, is making parser return I remember reading about this in gkossakowski/kentuckymule#6 (comment). |
It's a representation choice. With the current representation, we need the additional rule that normal packages are never members of the empty package, even if they are defined in it. So you could say that empty package on the outside of a tree signals "no package was given, therefore, nested packages go to the root package and all other nested definitions go to the empty package". I think that's a defensible representation choice, and it's not worth breaking Tasty compatibility in order to change it. But we might want to update the Tasty documentation to mention this fact. |
Example code:
Corresponding .tasty file:
i.e.
apackage
is nested in<empty>
package, as indicated by indentation and the addresses:<empty>
package continues until address 124.The text was updated successfully, but these errors were encountered: