3 ms·
> Blueprint is already basically Haskell It doesn't have lambdas/closures. You have to create a whole separate object in a separate file to pass something new
by cma 5y ago
> Blueprint is already basically Haskell
It doesn't have lambdas/closures. You have to create a whole separate object in a separate file to pass something new with data that can be called later.
- tinco 5y agoAlright, it's maybe a bit hyperbole. If I'm thinking about what characterises Haskell, it's not that it has closures, it's that it makes control flow and side effects explicit through monads. Blueprint has a very similar idea where effectful/stateful code is ordered sequentially through the white lines, while pure functions are hooked up just through their inputs and outputs. It doesn't go much deeper than that, but looking at Haskell it seems blueprint really might go a lot deeper.