Date: Tue, 18 Mar 2025 16:16:13 -0700
On Tuesday, 18 March 2025 14:16:51 Pacific Daylight Time Hans Ã…berg wrote:
> Features in a new language version that are not yet implemented can be
> marked, and the user will know, and at need implement, as in the example in
> my first post of this thread.
>
> One may need preprocessor macros so that when implemented by the compiler,
> the ones done by the user are inhibited.
> > Under what conditions would some code compile with the attribute, not
> > print
> > the warning, and would not compile with =delete?
>
> Compiler options can regulate that. The main point is that it is marked, so
> that the compiler can recognize the situation.
You have not answered the question. You've given a vague "behaviour could be
different" answer. I am asking what behaviour would be different:
Under what conditions would the compiler behave differently when attribute is
used compared to =delete("message")?
> Features in a new language version that are not yet implemented can be
> marked, and the user will know, and at need implement, as in the example in
> my first post of this thread.
>
> One may need preprocessor macros so that when implemented by the compiler,
> the ones done by the user are inhibited.
> > Under what conditions would some code compile with the attribute, not
> > the warning, and would not compile with =delete?
>
> Compiler options can regulate that. The main point is that it is marked, so
> that the compiler can recognize the situation.
You have not answered the question. You've given a vague "behaviour could be
different" answer. I am asking what behaviour would be different:
Under what conditions would the compiler behave differently when attribute is
used compared to =delete("message")?
-- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Principal Engineer - Intel DCAI Platform & System Engineering
Received on 2025-03-18 23:16:18