dnrops
/
rfcs
mirror of https://github.com/rust-lang/rfcs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add unresolved concern about naming

This commit is contained in:
Alice Ryhl 2024-05-24 17:33:28 +02:00
parent 17b4d18102
commit afe5534cb2
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
text/3621-derive-smart-pointer.md
View File

@ -752,7 +752,15 @@ feature, though it does so for a different reason than
# Unresolved questions
[unresolved-questions]: #unresolved-questions
No unresolved questions.
Bikeshedding over the name remains.
The name `#[derive(SmartPointer)]` leaves some things to be desired, as smart
pointers would generally want to implement some traits that this macro does
*not* expand to. Most prominently, any smart pointer should implement `Deref` or
`Receiver`. Really, the macro just says that this pointer works with unsizing
and dynamic dispatch.
We will settle on the final name prior to stabilization.
# Future possibilities
[future-possibilities]: #future-possibilities