Date: Fri, 20 Oct 2017 21:36:39 +0300
On 20 October 2017 at 21:23, Herb Sutter <herb.sutter_at_[hidden]> wrote:
> Furthermore, since we usually are in the business of standardizing things
> that users otherwise have to write many times themselves: Has SG10
> considered actively defining a <std-forward-compat> header library that does
> the above for all the things it can, the idea being that users who have to
> target multiple implementations at various stages of conformance can include
> <std-forward-compat> after all their standard library's own headers and
> write their code more closely against the actual latest IS's std:: library,
> without having to reinvent the above by hand (incompatibly on different
> systems), as a transition tool to help encourage people to adopt the latest
> standard?
>
> Nico, do you think that would be use, and if that were available would you
> recommend it?
What is the modular version of such an approach? Just out of curiosity
(I think a header like
that would be very useful).
> Furthermore, since we usually are in the business of standardizing things
> that users otherwise have to write many times themselves: Has SG10
> considered actively defining a <std-forward-compat> header library that does
> the above for all the things it can, the idea being that users who have to
> target multiple implementations at various stages of conformance can include
> <std-forward-compat> after all their standard library's own headers and
> write their code more closely against the actual latest IS's std:: library,
> without having to reinvent the above by hand (incompatibly on different
> systems), as a transition tool to help encourage people to adopt the latest
> standard?
>
> Nico, do you think that would be use, and if that were available would you
> recommend it?
What is the modular version of such an approach? Just out of curiosity
(I think a header like
that would be very useful).
Received on 2017-10-20 20:36:42