You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 2, 2019. It is now read-only.
Right now we send around T everywhere and it pervades everything. If a user wanted to use an enum type for this, it looks OK type-wise, but things get ugly if you wanted to use normal strings, as you now have Receiver<&'static str>, etc.
We should see if there's something we can do with the sink interface to allow us to pass in arbitrary keys so long as they fit an interface, something along the lines of what PathBuf does with AsRef<_>. We can store strings under the hood just fine, but we want a generic way to get to that point that holders of Receiver<T> and Sink<T> don't need to care about.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now we send around
T
everywhere and it pervades everything. If a user wanted to use an enum type for this, it looks OK type-wise, but things get ugly if you wanted to use normal strings, as you now haveReceiver<&'static str>
, etc.We should see if there's something we can do with the sink interface to allow us to pass in arbitrary keys so long as they fit an interface, something along the lines of what
PathBuf
does withAsRef<_>
. We can store strings under the hood just fine, but we want a generic way to get to that point that holders ofReceiver<T>
andSink<T>
don't need to care about.The text was updated successfully, but these errors were encountered: