Skip to content

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

Closed

Conversation

nicolasstucki
Copy link
Contributor

Based on #7324

odersky and others added 27 commits September 26, 2019 19:09
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.
Drop reflect-inline, since it did not do what one thought (called stdlib stripMargin
instead of locally defined one).

Move macros-in-same-project1 to run-macros

Fix error marker for macro-cycle1.scala.
Not needed right now, but might be useful in the future.
To avoid a compiler crash.
@nicolasstucki nicolasstucki self-assigned this Oct 3, 2019
Copy link
Member

@dottybot dottybot left a 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:

  1. Separate subject from body with a blank line
  2. When fixing an issue, start your commit message with Fix #<ISSUE-NBR>:
  3. Limit the subject line to 72 characters
  4. Capitalize the subject line
  5. Do not end the subject line with a period
  6. Use the imperative mood in the subject line ("Add" instead of "Added")
  7. Wrap the body at 80 characters
  8. Use the body to explain what and why vs. how

adapted from https://chris.beams.io/posts/git-commit

Have an awesome day! ☀️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants