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
We have no_default_derives now to disable the default derives/attrs. Perhaps we should add no_default_substitutions, which is more widely useful (ie usable with code generated to work with Subxt) and would allow users complete control over exactly which generated types are substituted and which are not?
Cons:
This will have some caveats like no_default_derives does (eg certain defaults are added to work around things like eg BTreeMap imposing Ord constraints on generated types), and I wouldn't expect most users to want it, but it would be consistent with allowing people to opt out of default derives and users could conditionally derive what was needed and override things as they wish to work around issues themselves.
I'm wary of supporting more use cases that don't revolve around using the macro to generate code for the Subxt library; I don't want us to end up with a bunch of complexity in the code to support more exotic uses that may be better off utilising their own codegen, since our macro stuff is geared towards generating a Subxt interface.
The text was updated successfully, but these errors were encountered:
We have
no_default_derives
now to disable the default derives/attrs. Perhaps we should addno_default_substitutions
, which is more widely useful (ie usable with code generated to work with Subxt) and would allow users complete control over exactly which generated types are substituted and which are not?Cons:
no_default_derives
does (eg certain defaults are added to work around things like egBTreeMap
imposingOrd
constraints on generated types), and I wouldn't expect most users to want it, but it would be consistent with allowing people to opt out of default derives and users could conditionally derive what was needed and override things as they wish to work around issues themselves.The text was updated successfully, but these errors were encountered: