August 23, 2016
https://issues.dlang.org/show_bug.cgi?id=16410

--- Comment #11 from Steven Schveighoffer <schveiguy@yahoo.com> ---
(In reply to Lodovico Giaretta from comment #10)
> (In reply to Lodovico Giaretta from comment #9)
> > Then a new question arises: why cannot attribute inference happen for *final* methods of templated classes?
> 
> Small precisation: I mean *final override* methods. For final (non-virtual) methods it already happens.

I think it should, where possible. That is, if you can override a non-@nogc method with a @nogc method (and if not, I think you should be able to), then inference of the attribute should happen for final methods.

--
January 10, 2021
https://issues.dlang.org/show_bug.cgi?id=16410

Bolpat <qs.il.paperinik@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |rejects-valid
                 CC|                            |qs.il.paperinik@gmail.com

--
November 10, 2022
https://issues.dlang.org/show_bug.cgi?id=16410

RazvanN <razvan.nitu1305@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |razvan.nitu1305@gmail.com
         Resolution|---                         |INVALID

--- Comment #12 from RazvanN <razvan.nitu1305@gmail.com> ---
(In reply to Lodovico Giaretta from comment #10)
> (In reply to Lodovico Giaretta from comment #9)
> > Then a new question arises: why cannot attribute inference happen for *final* methods of templated classes?
> 
> Small precisation: I mean *final override* methods. For final (non-virtual) methods it already happens.

The compiler cannot infer the attributes for final override methods because you already may have some constraints from the overriding function. For example, if the overriden function is @safe, the overriding function must also be @safe. Technically, the overriden function dictates the interface. I think it might be surprising to the attributes for overrides, even if they are final.

I think we can close this issue as INVALID.

--
1 2
Next ›   Last »