On 5 October 2017 at 23:50, Richard Smith <email@example.com> wrote:I can let users store the thing returned by the factory function as
> What benefit does the feature-test macro give you over using the
> non-guaranteed-copy-elision implementation in all cases?
they would store any object,
rather than force them to use lifetime-extending references.
Furthermore, if I decide that I really
hate having to use those references, I will disable the whole type if
guaranteed copy elision is not available.
This example I have is, as usual, not the only use case for a feature macro.