can't register io with reactor more than once, even in different tasks about async HOT 3 CLOSED

I've added a spec for this, demonstrating the issue. It's not a bug, but it's a semantic design decision.

subject.async do |task|
	socket = Async::TCPSocket.connect("localhost", port)
	
	# I'm not sure if this is the right behaviour or not. Without a significant amont of work, async sockets are tied to the task that creates them.
	expect do
		subject.async(socket) do |client|
			client.write(data)
			expect(client.read(512)).to be == data
		end
	end.to raise_error(ArgumentError, /already registered with selector/)
end

One option would be to add an unbind method which removes the socket from the current task and allows it to be used elsewhere for async function calls.

Also, if an exception happens in a situation like this - who is responsible for tidying up the dangling socket?

from async.

The dangling socket problem is solved using Task#with and Reactor#with. An unbind method is still not implemented.

from async.

It's now possible to use wrapped io in any task within the same reactor. It should be possible to unwrap or dup the IO to a different reactor as needed too.

from async.