You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ScheduleBuildSettings should have a report_sets option #7442
What problem does this solve or what need does it fill?
When attempting to resolve system order ambiguities, it can be very challenging to track down and eliminate ambiguities when multiple copies of the same system exist.
This is particularly common and brutal for apply_system_buffers, as we have many copies of this system in each schedule and they conflict with everything.
What solution would you like?
Add this field (off by default).
When this field is set to true, report all system sets that the conflicting systems are part of.
e.g apply_system_buffers (CoreSet::PostUpdateFlush), my_system (no sets)
Additional context
Please don't do this until #7267 is merged for the sake of my sanity.
Activity
Migrate engine to Schedule v3 (#7267)
Migrate engine to Schedule v3 (#7267)
Migrate engine to Schedule v3 (#7267)
Retain `::` after `>`, `)` or `]` when shortening type names (#7755)
Add `report_sets` option to `ScheduleBuildSettings` (#7756)
Migrate engine to Schedule v3 (bevyengine#7267)