mirror of
https://github.com/bevyengine/bevy
synced 2024-11-22 20:53:53 +00:00
9bce8712b5
Relying on TypeId being some hash internally isn't future-proof because there is no guarantee about internal layout or structure of TypeId. I benchmarked TypeId noop hasher vs fxhash and found that there is very little difference. Also fxhash is likely to be better supported because it is widely used in rustc itself. [Benchmarks of hashers](https://github.com/bevyengine/bevy/issues/1097) [Engine wide benchmarks](https://github.com/bevyengine/bevy/pull/1119#issuecomment-751361215) |
||
|---|---|---|
| .. | ||
| benches | ||
| macros | ||
| src | ||
| Cargo.toml | ||
| LICENSE_APACHE | ||
| LICENSE_MIT | ||
| README.md | ||
Bevy ECS
Bevy Engine's entity component system
Licensing
Bevy ECS has its roots in hecs, which is licensed as Apache 2.0. All original hecs code is licensed under Apache 2.0. All added/modified code is dual licensed under MIT and Apache 2.0. Files with an Apache 2.0 license header (with Google LLC as the copyright holder) were from the "original hecs" codebase. Files without the header were created by Bevy contributors.