multi-valued

A channel may be closed with the built-in function close; the multi-valued assignment form of the receive operator tests whether a channel has been closed.

The issue is that SQL reflects a more complicated multi-set multi-valued logical model.

You are storing entire multi-valued objects and your rows have variable number of columns & at times you are dealing with completely denormalized structure.

It's the engineering mindset at work: reduction to extremes can give you a good idea of whether or not something has a discrete solution or if it is multi-valued.

In practice, I don't think I've ever been annoyed by the syntax of Go. Perhaps the one iffy behaviour has been the way multi-valued := wriggles around mixed declaration/assignment dependant on what's already in scope.

In this case it seems to me that it is likely to be multi-valued but only in non-real-world scenarios and for all intent and purposes you might as well treat it as discrete: torture == bad.

I agree that you can model a multi-valued logic system on a universal Turing machine but you are wrong to think that doing this is the same as mapping to classical logic.