-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
[Merged by Bors] - Move ambiguity detection into its own file #5918
[Merged by Bors] - Move ambiguity detection into its own file #5918
Conversation
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.
Since this PR is part of a bigger plan, does make sense to have all planned features in an tracking issue? So we may know what to expect in the future, like adding back the removed tests.
I'm working off the plan in #4299 (comment) |
bors r+ |
(merged with one approval due to triviality) |
Pull request successfully merged into main. Build succeeded: |
# Objective This code is very disjoint, and the `stage.rs` file that it's in is already very long. All I've done is move the code and clean up the compiler errors that result. Followup to bevyengine#5916, split out from bevyengine#4299.
# Objective This code is very disjoint, and the `stage.rs` file that it's in is already very long. All I've done is move the code and clean up the compiler errors that result. Followup to bevyengine#5916, split out from bevyengine#4299.
# Objective This code is very disjoint, and the `stage.rs` file that it's in is already very long. All I've done is move the code and clean up the compiler errors that result. Followup to bevyengine#5916, split out from bevyengine#4299.
Objective
This code is very disjoint, and the
stage.rs
file that it's in is already very long.All I've done is move the code and clean up the compiler errors that result.
Followup to #5916, split out from #4299.