Leonard Brünings

> Btw, could we reuse BlockInfo if no GString is detected, and create a new instance only if an evaluation is needed? Maybe, with increased complexity.

@renatoathaydes, please take a look at the new `BlockListener` and `ErrorInfo` interfaces. I guess you are going to be one of the prime users of this feature, so if you...

@renatoathaydes, did you have a chance to take a look?

@mpiggott adding an optional reference class for the `ClassLoader` for the `ReflectionUtil` methods makes sense. This would require overloads for all methods that use a classloader. A PR would be...

> is it really such a performance hog that is has to be explicitly enabled? Hard to tell, for small code bases it is negligible, but for larger ones it...

FWIW implicit assertions in `if`-blocks are ignored, so even if we fix the compile error, I'm not sure that we'd treat the branches of the switch-expression as implicit conditions. In...

Spock assertions are not tested sequentially, unless you use separate `then` blocks. How would you see multiple timeouts interacting with each other? 1. In the same then `block` 1. Act...

> For me the fix shall make the behavior more alligned with the documentation and remove the current surprise, when you add a single unrelated interaction in the then block...

I think simply we can't simply forbid adding interactions in `when`, as you can define new mock objects and interactions in other interactions. So, a simple adding a `InteractionScope.freeze()` and...

Well, debuggers usually call `toString()` on the variables, so it is just reflecting what is actually happening. What would you expect happening, when you manually evaluate something in the debugger,...