Access serde attributes with reflection

[Leinnan]

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

Currently there is no way to know from type registration if given type does not have changed name of field, skiping serialization or providing default value if no field is present.

What solution would you like?

Could it be possible to build and store that information on build time for registered types?

[MrGVSV]

Copying my comments from Discord here for reference:

As for the serde stuff, I’m not sure we could effectively capture that. We could have it work only for the derived serde traits, but it wouldn’t be possible for manual implementors without adding one or more new reflection attributes to capture that information
And if we did want to capture serde attributes, I wonder if a more general approach would be to capture all attributes as a string that we store in type info
Of course concerns there would be the hit to binary size as well as macro expansion order (though I think derive macros can see all derive helper attributes on fields, I’d have to double check)

[Leinnan]

If binary size could be a problem maybe the feature could be opt out?