[Rivet] Dangerous casting to FinalState

[Andy Buckley]

Hmm, I certainly implemented it hoping that code with copy assignments (as
opposed to copy constructions, which should perhaps also be banned to
forbid an alternative-syntax route to achieving the same misguided goal)
would now fail to compile. I based that on some StackOverflow reading since
I was short of time to make an explicit test case of my own.

I was *hoping* (and convinced from that reading) that it would not be legal
for a private virtual method on a base class to be overloaded as public
(and certainly not *automatically*) on a derived class. It would be a huge
pain if those operators need to be *explicitly* private'd on every derived
Projection.

Aaaaand back to holiday ;-)
AB
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.hepforge.org/lists-archive/rivet/attachments/20150707/5d2971f3/attachment.html>