Quick question: In the API docs, we are told not to put nil values on a channel. Is this only because take from a closed channel returns nil, or for some other technical reason? I have searched around and haven't found an answer, but I just assume that because nil on a take means closed channel.

that's the reason

it'll throw an exception if you try to anyway

great, thanks!

also semantically what's the meaning of sending nil

there's no point IMHO

(similarly in datomic you can't store nil as a fact)

> It'll probably be awhile before I hear back from Rich, and I'm 90% sure the answer is "don't do that"

@ghadi Since we can store nil in data structures, I can see why some people might want to use it.

this isn't a data structure, this is communication between processes

Hey @ghadi...I got a message for you

nil

lol

that makes about as much sense as a nil on a channel 😉

it's communicating nothing to me