Jelte Fennema-Nio
Jelte Fennema-Nio
No real reason afaik. Just didn't spend time to test it yet/fix the compilation issues that likely occur. Feel free to submit a PR for PG15 compilation/testing.
Yeah makes sense, I would accept a fix for this issue. I think the easiest is to always add this `#[allow]` to the constructor field.
How long to wait for what?
Like I said in the comment you quoted: feel free to create a PR to do so... If no-one does that you can can wait a long time... That's why...
Afaict this is another instance of https://github.com/JelteF/derive_more/issues/348, it's a bit special because previously `AsMut` and `AsRef` had different implementations and thus different documentation. But my preference would be to remove...
I think this is very reasonable. I think the best solution would contain the following three things: 1. Allow providing an error type. This error type should have a `From`...
PRs for this feature are welcome (to be clear, any of the three features I described above features could be contributed separately in a PR).
For the cases you describe I agree it should be possible (at least the first one, the second one might be harder). So no technical reason, just no-one implemented it...
@BenLeadbetter I think you're making this more complicated than necessary. We can use the same approach that we use for structs with multiple fields here: Adding a `#[deref]` attribute to...
Can you share codesnipped that causes this warning? Also could you try with this PR: https://github.com/JelteF/derive_more/pull/377 That should solve the "not yet implemented" error.