Subsume put! into push!?

[malmaud]

Now that RemoteRefs can store an array of values, it might sense to just eliminate put! and instead push! values into RemoteRefs and Channels.

[jakebolewski]

@amitmurthy I think we want to retain put! for RemoteRef's but adding push! to channels seems like a good idea.

[amitmurthy]

The Channels API mirrors the RemoteRef API. Also RemoteRef's point to AbstractChannels. Any concrete implementation of an AbstractChannels must implement put!, take!, fetch, isready and wait. We can look at renaming put!, take! and fetch, but we should continue to keep the Channel API in sync with RemoteRef.

[jakebolewski]

is there any way to push an iterable to a channel without having to splat it?

[amitmurthy]

No.

I think I misunderstood your comment. Yes, we can add push! while retaining put!.

[malmaud]

I think it would make sense to do so, since from the user's point of view a channel is just a deque with special blocking semantics.

[malmaud]

Closed by #13538