[Cppqed-support] interaction as template parameter

[Raimar S. <rai...@ui...>]

Dear András,

I am currently trying to understand the new shared pointer branch and to adapt 
the Python interface accordingly. 

Why is the interaction now a template argument, e.g. in binary::make and the 
constructor of Act? Unfortunately this further complicates exposing these 
functions to Python.

For binary::make it is possible to work around it by exposing binary::doMake 
directly instead. For Act we would have to take the specific interaction into 
account when we decide if a new Act-instantiation has to be compiled for 
Python on demand, so we have to compile more often.

I do not understand why the template is needed in the first place. Why not 
deduce the Interaction class from SubSystemsInteraction as before? This way 
the same instantiation can be used for every Interaction with the correct 
rank.

Best regards,
Raimar