Open bushrat011899 opened 1 month ago
This should be part of the Bevy extended universe, over with atomiccow
. The name of the crate should not have "Bevy" in it to encourage broader adoption.
To commence the bikeshedding, I propose polytuple
as a name.
variadics_please
gets my vote.
Oh in line with the not-BSN crate, i-cant-believe-its-not-variadics
I like variadics_please
, but maybe we should also consider keeping the name all_tuples
(assuming someone else hasn't taken it)? Especially considering it's a fairly known about macro in the community.
I think that putting variadics
into the crate name in some form is helpful for searchability. I also think it's a natural home for any other variadic-related functionality that Bevy or other users might need.
Since bevy_utils/macros
only contains all_tuples!
and all_tuples_with_size!
, it seems like the steps are pretty straightforward:
variadics_please
on crates.iobevyengine/variadics_please
bevy_utils/macros
into the new repo, polish the documentation, etc.bevy_utils
to re-export variadics_please
, or update the other crates to directly use variadics_please
instead.
Originally posted by @alice-i-cecile in https://github.com/bevyengine/bevy/issues/15936#issuecomment-2415352291