[Rivet] Using a projection "on the fly"

[Hendrik Hoeth]

Thus spake Andy Buckley (andy.buckley at ed.ac.uk):

> Just call the normal constructor, like you would in the init method.
> You can supply a FinalState object by reference via (IIRC) a call to
> getProjection<FinalState>("MyFS").

Wow, that's subtle. I solved my problem by adding a Thrust(){}
constructor, i.e. a constructor that doesn't require an input final
state. Are there any reasons why we shouldn't do this? Like this I don't
have to create an empty (read: fake) final state.

     Hendrik

-- 
It pays to be obvious, especially if you have
a reputation for subtlety.    -- Isaac Asimov