[Rivet] Dangerous casting to FinalState

David Grellscheid david.grellscheid at durham.ac.uk
Tue Jul 14 19:22:14 BST 2015


> For the following major release, it'd be good to solve this more
> completely. FinalStates are the only significant subset of projections
> which can have this problem, because FinalState itself is not virtual.

I don't understand what you mean here. Classes cannot be virtual / 
non-virtual, only methods can. A method is virtual if it has been marked 
so anywhere up the inheritance tree, it's not necessary to re-mark it as 
virtual in each child class.

   David


More information about the Rivet mailing list