Skip to content

Conversation

powerboat9
Copy link
Collaborator

@powerboat9 powerboat9 commented Aug 9, 2025

This should prevent issues like #3444 from affecting compilation of libcore 1.49

(when applied after #4052 at least, so that should be merged first to make the commit messages correct)

@powerboat9 powerboat9 marked this pull request as draft August 10, 2025 02:13
@powerboat9 powerboat9 changed the title Properly expand macro in ErrorPropagationExpr Improve macro expansion for libcore Aug 10, 2025
@powerboat9 powerboat9 marked this pull request as ready for review August 10, 2025 14:40
Copy link
Member

@CohenArthur CohenArthur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, do we need to add testcases for this?

@powerboat9 powerboat9 marked this pull request as draft August 12, 2025 01:10
@powerboat9
Copy link
Collaborator Author

Looks like #4099 will supersede this

@P-E-P
Copy link
Member

P-E-P commented Oct 1, 2025

@powerboat9 Should we close this PR ?

@powerboat9 powerboat9 force-pushed the handle-que branch 2 times, most recently from 6867077 to 83f6117 Compare October 2, 2025 22:25
@powerboat9
Copy link
Collaborator Author

Most of this was made redundant, but it looks like some ErrorPropagationExpr handling is still missing.

@powerboat9 powerboat9 marked this pull request as ready for review October 2, 2025 22:27
gcc/rust/ChangeLog:

	* ast/rust-ast-pointer-visitor.cc (PointerVisitor::visit):
	Handle the expression contained in an ErrorPropagationExpr.
	* ast/rust-ast-visitor.cc (DefaultASTVisitor::visit): Likewise.

Signed-off-by: Owen Avery <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants