Fix case-insensitive comparison of channel names#250
Merged
Conversation
osa1
force-pushed
the
chan_name_type
branch
2 times, most recently
from
September 19, 2020 03:18
c4951d9 to
c34a6ab
Compare
osa1
force-pushed
the
chan_name_type
branch
2 times, most recently
from
September 20, 2020 10:41
55e9474 to
e81ec8b
Compare
This sets the stage for #248. See the documentation in the new crate and the ChanName type for details.
osa1
force-pushed
the
chan_name_type
branch
from
September 20, 2020 11:45
e81ec8b to
b5fbe32
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
See the documentation in code for details.
Will fix #248 when complete.
I want to merge #249 first as this will touch the same code and there will be lots of merge conflicts.