Have a dedicated visitor for lambda generation from driver

So far, we used a global context to tell the normal visitor,
that it is generating for driver code. This was feasible, as
we only had one differing implementation. With more differences,
it is better style to derive from the visitor and implement
the differences there.