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
Copy file name to clipboardExpand all lines: content/learn/migration-guides/0.15-to-0.16.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,6 @@ The most important changes to be aware of this release are:
14
14
15
15
- Bevy has reworked its error handling to make it easier to handle `Result`s everywhere. As a result, `Query::single` and friends now return results, rather than panicking.
16
16
- Bevy's ECS now has built-in one-to-many entity relationships. The existing parent-child hierarchy system has been modified to use these relationships, causing minor breaking changes in entity despawning behavior and how children are added / replaced for a parent entity.
17
-
- The `bevy` crate now supports `no_std` platforms. As part of this, many items (like `HashMap`) from `bevy_utils` have been moved into `bevy_platform_support`. If you are the author of an ecosystem crate, you may want to offer `no_std` support to your users as well: it's generally straightforward unless you're interfacing directly with the underlying operating system.
17
+
- The `bevy` crate now supports `no_std` platforms. As part of this, many items (like `HashMap`) from `bevy_utils` have been moved into `bevy_platform`. If you are the author of an ecosystem crate, you may want to offer `no_std` support to your users as well: it's generally straightforward unless you're interfacing directly with the underlying operating system.
@@ -87,7 +87,7 @@ now rely on `bevy_log` instead (or `tracing` itself, being sure to keep the vers
87
87
```
88
88
89
89
-`hashbrown` was removed from `bevy_utils` as a re-export due to its significant API change from `hashbrown` 0.14 to 0.15.
90
-
Instead of exposing a large public API out of our direct control, we've taken a more explicit subset and moved it into `bevy_platform_support::collections`, mimicking the layout of the standard library.
90
+
Instead of exposing a large public API out of our direct control, we've taken a more explicit subset and moved it into `bevy_platform::collections`, mimicking the layout of the standard library.
91
91
If you need access to `hashbrown`, take a direct dependency instead.
92
92
93
93
-`detailed_trace` was removed due to its minimal use within the engine.
0 commit comments