Skip to content
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

Dyno: Resolve auto module visibility statements eagerly #26461

Merged
merged 1 commit into from
Jan 6, 2025

Conversation

DanilaFe
Copy link
Contributor

@DanilaFe DanilaFe commented Jan 3, 2025

This incurs a penalty up front, but prevents odd ordering properties in the query system. It's a workaround for a query system bug detailed in #26459.

This way, cycles in the standard module dependency graph are always visited in the same order (starting with ChapelBase). As a result, we don't create cycles over multiple generations. This workaround does not prevent the issue from occurring in other contexts, such as user projects with circular dependencies.

Reviewed by @benharsh -- thanks!

Testing

  • Anna's test branch doesn't crash

This incurs a penalty up front, but prevents odd ordering properties
in the query system. It's a workaround for a query system bug
detailed in chapel-lang#26459.

Signed-off-by: Danila Fedorin <[email protected]>
@DanilaFe DanilaFe changed the title Resolve auto module visibility statements eagerly Dyno: Resolve auto module visibility statements eagerly Jan 3, 2025
@DanilaFe DanilaFe requested a review from benharsh January 6, 2025 19:28
@DanilaFe DanilaFe merged commit 3ce06c9 into chapel-lang:main Jan 6, 2025
8 checks passed
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.

2 participants