I’ve been going back and forth on those two syntax...
# kobalt
p
I’ve been going back and forth on those two syntaxes for some internal things. The type safe builder pattern is nice (as has been mentioned) since it allows other arbitrary code to be executed within the lambda's scope. But with the lambda syntax and no other parameters, there is no way of enforcing (at compile time) anything that is required, if that’s something that’s needed (unless I’ve missed something). Using a “normal" function call does enable that.