3 ms·
I'm not talking about what Go is; I'm more interested in what it might have been. There's nothing in the law that prevents mapping with side effects. If the sid
by jacques_chester 13y ago
I'm not talking about what Go is; I'm more interested in what it might have been. There's nothing in the law that prevents mapping with side effects. If the side-effects don't require a particular order, why constrain them?
- icebraining 13y agoI'm not talking about what Go is; I'm more interested in what it might have been. Well yes, but there are certain core concepts that define Go, and being imperative with side-effects is one of them. If we drop that, then we're no longer discussing Go but some hypothetical language. There's nothing in the law that prevents mapping with side effects. If the side-effects don't require a particular order, why constrain them? But they aren't constrained, they just aren't built-in. Go has loops, not maps, but if one wants to make a mapping function, the link I posted shows there's no constraint in having it execute out of order.
- jacques_chester 13y agoI think we're just restating our arguments. I'm happy to leave it here.