Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reflection: type aliases #12387

Open
viridia opened this issue Mar 9, 2024 · 1 comment
Open

Reflection: type aliases #12387

viridia opened this issue Mar 9, 2024 · 1 comment
Labels
A-Reflection Runtime information about types C-Feature A new feature, making something new possible

Comments

@viridia
Copy link
Contributor

viridia commented Mar 9, 2024

What problem does this solve or what need does it fill?

The ability to define reflection type names that are both stable and reasonably succinct would be valuable, particularly in cases involving evolution of asset formats:

What solution would you like?

From the discord:

#[reflect(Reflect)]
#[type_path(alias = scenery::FloorSurface)]
struct StdFloorSurface { .. }

Additional context

There's a PR #5830 which attempts to solve this problem in a slightly different way.

@viridia viridia added C-Feature A new feature, making something new possible S-Needs-Triage This issue needs to be labelled labels Mar 9, 2024
@alice-i-cecile alice-i-cecile added A-Reflection Runtime information about types and removed S-Needs-Triage This issue needs to be labelled labels Mar 9, 2024
@alice-i-cecile
Copy link
Member

#3877 is related, as it discusses the patterns by which we could define stable, artist-friendly names for serialized data.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Reflection Runtime information about types C-Feature A new feature, making something new possible
Projects
None yet
Development

No branches or pull requests

2 participants