Most of the committee hates that you can overload operator&, particularly the library implementors, who need to sprinkle std::addressof() everywhere to fight against it.Of course when using operator&() if there is any previous pointer it will be destroyed by reset(); as it can be seen from my example.Please provide feedback and suggestions. :)
--Be seeing you,Tony
--
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposal...@isocpp.org.
To post to this group, send email to std-pr...@isocpp.org.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/d86a203b-ca5e-43f1-8783-5d0d76f079d8%40isocpp.org.
pointer* operator&(){reset();return &_ptr;}
--
You received this message because you are subscribed to the Google Groups "ISO C++ Standard - Future Proposals" group.
To unsubscribe from this group and stop receiving emails from it, send an email to std-proposals+unsubscribe@isocpp.org.
To post to this group, send email to std-pr...@isocpp.org.
To view this discussion on the web visit https://groups.google.com/a/isocpp.org/d/msgid/std-proposals/CANh8DEn4X%2BTugRixQxFpwa5P47t7SLn1xVzPyJ20hE0OeHfnKw%40mail.gmail.com.
(LPVOID*)locator.release()
--
Zhihao Yuan, ID lichray
The best way to predict the future is to invent it.
_______________________________________________