-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Collect macro dependencies #7362
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
Collect macro dependencies #7362
Conversation
Allows macros to be defined and called in the same project. The idea is to suspend the callers of a macro (and their upstream dependencies), compile the sourcefile(s) containing the macro(s), and then compile the suspended files in a second run. The scheme detects and flags as errors calls to macros in the same file and mutual dependcies between different files which would not work with suspensions. It needs to be complements by another mechanism that detects that class files loaded by a macro class loader do not have assiciated source files that are currently compiled.
Using a Set risks giving different results in different runs.
The real thing that needs to be tracked for cyclic dependencies are calls to spliced methods. Move the suspend machinery from inline calls to these.
Not needed right now, but might be useful in the future.
This reverts commit 8cea720.
To avoid a compiler crash.
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.
Hello, and thank you for opening this PR! 🎉
All contributors have signed the CLA, thank you! ❤️
Commit Messages
We want to keep history, but for that to actually be useful we have
some rules on how to format our commit messages (relevant xkcd).
Please stick to these guidelines for commit messages:
- Separate subject from body with a blank line
- When fixing an issue, start your commit message with
Fix #<ISSUE-NBR>:
- Limit the subject line to 72 characters
- Capitalize the subject line
- Do not end the subject line with a period
- Use the imperative mood in the subject line ("Add" instead of "Added")
- Wrap the body at 80 characters
- Use the body to explain what and why vs. how
adapted from https://chris.beams.io/posts/git-commit
Have an awesome day! ☀️
Based on #7324