Date: Tue, 02 Jul 2024 18:07:46 +0200
On Tuesday 2 July 2024 17:52:18 CEST Marcin Jaczewski wrote:
> > It's also easy to work around: #include a more precise header, like
> > fstream, strstream, ostream, etc.
>
> And this will not be needed when I use `import std;` in future version of
> GCC?
I don't know. If it does emit that snippet with the import, it's a QoI issue
that should be fixed there.
> > It's also easy to work around: #include a more precise header, like
> > fstream, strstream, ostream, etc.
>
> And this will not be needed when I use `import std;` in future version of
> GCC?
I don't know. If it does emit that snippet with the import, it's a QoI issue
that should be fixed there.
-- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Principal Engineer - Intel DCAI Platform & System Engineering
Received on 2024-07-02 16:07:51