-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add requiredXYZ symbols to TASTy reflect context #7903
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
Add requiredXYZ symbols to TASTy reflect context #7903
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Otherwise, LGTM
def Context_requiredClass(self: Context)(path: String): Symbol | ||
|
||
/** Get module symbol if module is either defined in current compilation run or present on classpath. */ | ||
def Context_requiredModule(self: Context)(path: String): Symbol |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The meta-programmer may not know what's a module. Maybe rename to requiredObject
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Better to keep names consistent. It will be simpler for documentation. We also have moduleClass
and companionModule
that use the same naming scheme.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I totally agree, for advanced meta-programming, keeping the concepts closer to the compiler will help both meta-programmers who want to get into the compiler and maintenance of the framework.
No description provided.