-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could crates.io require updating with the master branch on GitHub? #58
Comments
Of course I understand that the master branch and what's officially out there can be out of sync, but it seems that the change to signal the end of the stream is a fairly important one? Unless I'm missing something in the source that I see on crates.io (which is very likely) |
Hi, yes, the master branch is the current (active) state, the latest versions of
Yes. The version from master branch has not yet been published. The changes you're referring to have been made to implement some improvements which were suggested to us, namely we changed the semantics for the Some people already mentioned in multiple comments that we have to publish |
Ok gotcha, thank you for explaining! |
extract the context values from `WebSocket`
Hello, I'm new to Rust so I'm probably just a bit confused but I was looking through the docs for what appears to be the latest version of tokio-tungstenite on crates.io (v0.6.0), specifically the source for WebSocketStream in lib.rs (https://docs.rs/tokio-tungstenite/0.6.0/src/tokio_tungstenite/lib.rs.html#162-164), and it appears that the code for WebSocketStream is a fair bit different to that on the GitHub master branch. For example, comparing the struct and the poll function in 'impl Stream for WebSocketStream':
(crates.io source)
(GitHub source)
(crates.io source)
(GitHub source)
At least for me I can confirm that when I add 'tokio-tungstenite = "*"' to my Cargo.toml it uses the code that I can see on crates.io. Is this the case for anyone else?
(Edit: changed format for code blocks)
The text was updated successfully, but these errors were encountered: