We're updating the issue view to help you get more done. 

Clarify timeout doc to mention that close! should not be called on a timeout channel

Description

After running into a race-condition involving closed timeout channels, it seems like it would be appropriate to mention that `close!` should never be called on a timeout channel in its docstring. The attached patch tweaks the doc string to that effect. Please advise if you'd like the wording changed a bit.

Environment

None

Status

Assignee

Unassigned

Reporter

import

Approval

None

Patch

Code

Priority

Major