1b7db895b7
This pr uses the `extern crate self as` trick to make proc macros behave the same way inside and outside bevy. # Objective - Removes noise introduced by `crate as` in the whole bevy repo. - Fixes #17004. - Hardens proc macro path resolution. ## TODO - [x] `BevyManifest` needs cleanup. - [x] Cleanup remaining `crate as`. - [x] Add proper integration tests to the ci. ## Notes - `cargo-manifest-proc-macros` is written by me and based/inspired by the old `BevyManifest` implementation and [`bkchr/proc-macro-crate`](https://github.com/bkchr/proc-macro-crate). - What do you think about the new integration test machinery I added to the `ci`? More and better integration tests can be added at a later stage. The goal of these integration tests is to simulate an actual separate crate that uses bevy. Ideally they would lightly touch all bevy crates. ## Testing - Needs RA test - Needs testing from other users - Others need to run at least `cargo run -p ci integration-test` and verify that they work. --------- Co-authored-by: Alice Cecile <alice.i.cecile@gmail.com>
9 lines
321 B
Rust
9 lines
321 B
Rust
use crate::impl_type_path;
|
|
|
|
impl_type_path!(::foldhash::fast::FoldHasher);
|
|
impl_type_path!(::foldhash::fast::FixedState);
|
|
impl_type_path!(::foldhash::fast::RandomState);
|
|
impl_type_path!(::foldhash::quality::FoldHasher);
|
|
impl_type_path!(::foldhash::quality::FixedState);
|
|
impl_type_path!(::foldhash::quality::RandomState);
|