-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Revert "[SwiftLexicalLookup] New unqualified lookup implementation validation" #78280
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
Revert "[SwiftLexicalLookup] New unqualified lookup implementation validation" #78280
Conversation
@MAJKFL I believe the issue here is that there's now a cycle from swiftAST -> swiftASTGen -> swiftAST. It passed on PR testing as it uses Ubuntu 20.04 and ends up using |
@swift-ci please smoke test |
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.
Ah, I see there’s a cycle. Thank you for caching that! It does seem to be a bit tricky to fix. I don’t think it would be possible to move the validation outside of ASTGen
as it uses it to e.g. access cached if config configured regions, or the parsed source file itself.
Would it make sense to move the logic somewhere outside of swiftAST
, or to possibly inject LoggingASTScopeDeclConsumer
at all unqualified lookup entry points? If it’s not a viable option, do you perhaps have any suggestions for an alternative approach? @bnbarham @DougGregor
I think it's a good idea to revert it for now and I'll look into fixing it in a subsequent PR.
I think the easiest thing here would probably be to have a new Swift module, ie. move EDIT: I just noticed you said:
I'd need to look into that more, it does seem like it should be possible to split them 🤔. We probably need to split out more of |
I think the original PR introduces the new dll |
Thanks @hjyamauchi, will indeed need to add to swift-installer-scripts too. |
I will see if we can extract ExportedSourceFile related code out of |
Reverts #77140 as it causes nightly toolchain failures for Debian 12/Fedora 39/Ubuntu 24.04.