[Random Thought] std::sync::mpsc in a separate library?

libs
1

I know it is already stable. Moving it would break things.

However, as it seemed reasonable to keep crates like rand shipped alone, it seems mpsc should be a crate of its own too?

I wonder if there’s other considerations?

I admit that it is the unstable macro select! (which seems really odd in the list of macros exported by libstd, maybe a macro with that name is something that should be exported by futures-rs!) that actually makes me think it bad there…

2

Pretty soon we could export select! using the new macro naming mechanism, which allows one to use macros just like other things. Would that address your concern?

3

@nikomatsakis Yeah, that would be great.

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.