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
A-UtilsUtility functions and typesC-Code-QualityA section of code that is hard to understand or changeD-TrivialNice and easy! A great choice to get started with Bevy
# Objective
- The exported hashtypes are just re-exports from hashbrown, we want to
drop that dependency and (in the future) let the user import their own
choice.
- Fixes#11717
## Solution
- Adding a deprecated tag on the re-exports, so in future releases these
can be safely removed.
A-UtilsUtility functions and typesC-Code-QualityA section of code that is hard to understand or changeD-TrivialNice and easy! A great choice to get started with Bevy
What problem does this solve or what need does it fill?
As discussed in #11690, Bevy no longer uses these types internally.
What solution would you like?
Because these are simple re-export of HashBrown types, we should just remove them from Bevy, and let users import the types themselves if needed.
Deprecating for a cycle offers a smoother migration path, as we can point users to the correct replacement.
What alternative(s) have you considered?
Just remove them immediately, which is slightly less worse but more annoying to migrate for users.
Keeping them is a poor choice, as we have no business owning all purpose hashmap types. See #11478.
The text was updated successfully, but these errors were encountered: