RFC: Deprecate and later remove the in-tree url crate #189
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
👍 |
|
Since this has been started, shouldn't this RFC be accepted? |
|
Yes, thanks @SimonSapin! |
|
@alexcrichton, any opinion on how long the deprecation cycle should be? Should we have a general policy on this? (Perhaps we don’t need to be that formal before 1.0) |
|
I would expect liburl to stick around for at least until 0.12.0 is released. |
withoutboats
pushed a commit
to withoutboats/rfcs
that referenced
this pull request
Jan 15, 2017
Allow public access to the channel Sender error type
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rendered view