Re:Mistakes with Rust smart pointers: when Deref goes wrong
by saghm on Monday July 10, 2023 @08:27PM
(#36674986)
Am I correct in thinking this is the type of thing change that fits the criteria to be implemented in a new edition? Assuming the issue is the same one I often run into (i.e. 'a versus for<'a>), it seems like special casing this for closures passed as arguments would be quite nice, but the fact that it wasn't done for 2018 or 2021 makes me think that maybe it's not something that would qualify for introducing in this way.
[ Parent
| on HN ]
Re:Mistakes with Rust smart pointers: when Deref goes wrong
by tialaramex on Tuesday July 11, 2023 @04:06AM
(#36677859)
It's not "just" syntax, so it couldn't "just" be a new edition, but I suppose it's conceivable that a hack could be invented and then the old behaviour grandfathered into prior editions as was done for impl IntoIterator for [T; N] in 2021 Edition.
That's a heavy lift though, you may need to carry this special code around in every compiler, forever, and I haven't even figured out what such code should look like, it might be really hard to even write it.