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
I know from reading past issues and PRs, that the way the trait tree looks now is because of historical reasons and chaning it is out of the question. But this brings a pretty big limitation with it: because AnyBitPattern has a blanket impl where T: Pod, this means an array [T; N] where T: AnyBitPattern is not AnyBitPattern. This in turn causes the derive macro not to work when a struct contains such a field. Is this something that you would consider fixing (the derive macro)? If so I would happily work on it.
The text was updated successfully, but these errors were encountered:
I know from reading past issues and PRs, that the way the trait tree looks now is because of historical reasons and chaning it is out of the question. But this brings a pretty big limitation with it: because
AnyBitPattern
has a blanket impl whereT: Pod
, this means an array[T; N] where T: AnyBitPattern
is notAnyBitPattern
. This in turn causes the derive macro not to work when a struct contains such a field. Is this something that you would consider fixing (the derive macro)? If so I would happily work on it.The text was updated successfully, but these errors were encountered: