<@U0BHS1Y07> there's more to it than just performa...
# language-proposals
@voddan there's more to it than just performance concerns. It's simply about minimizing the scope that you have access to. I'd argue I could write code with far more confidence if I knew that my lambdas didn't access any outside members, or only accessed certain outside members. It would be a valid use-case simply to consider any common collection-mutating stream, or a bunch of chained Rx operators. You could have 4 or 5 (or more!) lambdas all in succession, and if you can enforce the fact that outside members can't be accessed, it makes the code a lot safer to read