Date: Wed, 12 Feb 2025 09:55:53 +0000
On Tue, 11 Feb 2025 at 23:59, Chris Ryan via Std-Proposals <
std-proposals_at_[hidden]> wrote:
> > I'm not so sure about the "will be there for a long time".
> AND
> > It may not be by C++26, but hopefully eventually, things seem to be
> going in that direction.
>
> Legacy compatibility says that you can not break something that works,
> not just 'nobody uses it' or 'you don't like it'. BTW streaming is
> actually heavily used.
>
> It has been there long before you existed and it will still be there until
> the language ends.
>
>
Agreed. There's no justification for removing iostreams, even if there are
other "better" alternatives available in the standard.
iostreams are not broken or wrong, and will continue to be widely used even
if some people migrate completely to std::print, std::scan, or other
features.
std-proposals_at_[hidden]> wrote:
> > I'm not so sure about the "will be there for a long time".
> AND
> > It may not be by C++26, but hopefully eventually, things seem to be
> going in that direction.
>
> Legacy compatibility says that you can not break something that works,
> not just 'nobody uses it' or 'you don't like it'. BTW streaming is
> actually heavily used.
>
> It has been there long before you existed and it will still be there until
> the language ends.
>
>
Agreed. There's no justification for removing iostreams, even if there are
other "better" alternatives available in the standard.
iostreams are not broken or wrong, and will continue to be widely used even
if some people migrate completely to std::print, std::scan, or other
features.
Received on 2025-02-12 09:56:13