On Wednesday, 10 August 2016 at 15:48:10 UTC, Lodovico Giaretta
wrote:
On Wednesday, 10 August 2016 at 15:39:19 UTC, Arafel wrote:
Would it even make sense to "force" (deprecation warning) a
"final" keyword in any implicitly-final function (I wasn't
even aware of those, I have to admit)? It would make things
much clearer, like with "override"...
I read the spec again, and found out that it says interfaces
cannot contain templated functions... So either my
interpretation is the intended one and the spec is outdated, or
the spec is right and the compiler is bugged.
Anyway what I said about implicit final is true for classes. In
classes, I don't like the idea of having to put an explicit
final, but this is debatable. For interfaces, I'm ok with forcing
an explicit final attribute (but as I said the spec does not
allow templated functions in interfaces, even if the compiler
does).
