On Tuesday, 18 March 2025 12:44:30 Pacific Daylight Time Hans Åberg via Std-
Proposals wrote:
> With an error, one must handle the case when the definition is in a source
> file and the unimplemented directive in a header file, which must be
> overridden somehow if used in another source file. With a warning one gets
> a correct compile.

Sorry, not following this sentence. Either a method is implemented or it's not
implemented. There's no such thing as a schrödinmethod that is both
implemented and unimplemented. So if the method is marked unimplemented in a
header, then no source file will think it's implemented.

What's the point of making it a warning?

Under what conditions would some code compile with the attribute, not print
the warning, and would not compile with =delete?

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Principal Engineer - Intel DCAI Platform & System Engineering