Add desugaring to fixed point #4080
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
CohenArthur
force-pushed
the
fixed-point-desugar
branch
from
eff7800 to
433205c
Compare
gcc/rust/ChangeLog: * ast/rust-desugar-apit.cc: Mark as clean when starting a desugar, and as dirty when actually doing a desugar. * ast/rust-expression-yeast.cc (ExpressionYeast::go): Likewise. * ast/rust-desugar-apit.h: Add dirty flag. * ast/rust-expression-yeast.h: Likewise. * rust-session-manager.cc (Session::expansion): Move desugars to fixed point.
|
I don't think desugaring needs to be fixed point -- unless the resolver is supposed to rely on things being desugared to complete resolution? It seems like the macro issues are all problems local to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Marking this as a draft since it might not be what we actually want, but we do get a lot further when expanding macros in
core. For example, things likewrite!(fmt, ...)?;now work properly. Note that this may also be because the ExpandVisitor is lacking in many places... so just looking for comments on this for now