Groovy should not be a dependency, but if it exists on the classpath, we should fit right in (after all we are using Spock)
[x] Take advantage of Closure->Lambda conversion.
[x] Make sure classes are usable as categories i.t. the first method is sensible as self (do not do that at the expense of consistency on the Java side)
[x] Add extension methods for peek and poke field to classes
ddimtirov
commented
7 years ago
Groovy should not be a dependency, but if it exists on the classpath, we should fit right in (after all we are using Spock)
self(do not do that at the expense of consistency on the Java side)