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
This problem can be worked around by storing all the values in a tuple (and I've done this in situations where casey doesn't work) but I feel individually named variables are more readable when expanding output using cargo expand.
I think the convenience of this crate could be improved by adding two more meta variables.
#member0
The member name but in lower case.
#_member0
The member name but in lower case and starting with an underscore.
The text was updated successfully, but these errors were encountered:
Great library, saves me a ton of time and effort.
I'm using it to create an ECS framework for retro consoles.
I've ran into situations where I need to generate variables referencing each member of the tuple. For now I just use a crate called casey to convert the member names to lowercase: https://github.com/IamTheCarl/micro_ecs/blob/master/src/storage/tuples.rs#L33
This problem can be worked around by storing all the values in a tuple (and I've done this in situations where casey doesn't work) but I feel individually named variables are more readable when expanding output using cargo expand.
I think the convenience of this crate could be improved by adding two more meta variables.
The text was updated successfully, but these errors were encountered: