Since we're not calling this lambda from inside a method, the `return` causes a LocalJumpError on 1.8.x. It appears this functionality works fine on 1.9.x but we'd like to support both. The correct behavior appears to use `next`.
Since we're not calling this lambda from inside a method, the `return` causes a LocalJumpError on 1.8.x. It appears this functionality works fine on 1.9.x but we'd like to support both. The correct behavior appears to use `next`.