Yutao Yuan aabc47f290 Make public macros more robust with $crate (#4655) ... # Objective We have some macros that are public but only used internally for now. They fail on user's code due to the use of crate names like `bevy_utils`, while the user only has `bevy::utils`. There are two affected macros. - `bevy_utils::define_label`: it may be useful in user's code for defining custom kinds of label traits (this is why I made this PR). - `bevy_asset::load_internal_asset`: not useful currently due to limitations of the debug asset server, but this may change in the future. ## Solution We can make them work by using `$crate` instead of names of their own crates, which can refer to the macro's defining crate regardless of the user's setup. Even though our objective is rather low-priority here, the solution adds no maintenance cost so it is still worthwhile.		2022-05-06 19:29:45 +00:00
..
src	Make public macros more robust with $crate (#4655)	2022-05-06 19:29:45 +00:00
Cargo.toml	Bump Bevy to 0.8.0-dev (#4505)	2022-04-17 23:04:52 +00:00