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
## Synopsis
This PR is a part of replacing all attributes having `syn::Meta` syntax
to custom parsing, similarly to #241, #248.
Paves the way for #285, and possibly other enhancements such as an
opt-in #123.
## Solution
Implement custom attribute parsing without `utils::State`.
Co-authored-by: Kai Ren <tyranron@gmail.com>
Resolves#285
## Synopsis
The `AsRef`/`AsMut` derives were less powerful than `From` and `Into`,
because there's no way to specify types into which forwarded
implementations should convert.
## Solution
Keep using the `forward` attribute argument for blanket forwarded impls,
and use a list of types for selective ones.
Co-authored-by: tyranron <tyranron@gmail.com>
Currently there are 2 options for
AsRef
derives:[as_ref(forward)]
, which generates a generic impl for all types the field can be converted toIt would be useful to be able to list types for implementation explicitly, like with From
For example
This wouldn't work with
[as_ref(forward)]
, since we'd have conflicting implementations forAsRef<[u8]>
.The text was updated successfully, but these errors were encountered: