On Friday, 6 April 2018 at 17:46:26 UTC, Per Nordlöw wrote:
Why isn't `std.conv.emplaceRef` public when `std.conv.emplace` is?


emplaceRef(x, ...)

is a bit more @safe than

emplace(&x, ...)


I had the same thoughts too:


We can even do this without introducing a new symbol, but simply let emplace accept pointers and ref like we need with formattedRead for nice backwards compatibility.
  • Making emplaceRef public Per Nordlöw via Digitalmars-d-learn
    • Re: Making emplaceRef public Seb via Digitalmars-d-learn

Reply via email to