Discussion: Make 'client' an optional feature? #163
Closed
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.
This PR enables using just the
irc::proto
part of the crate, without building theirc::client
part.This allows dropping >70% of the deps, including
native-tls
which fails horribly to build on anything fun.The changes are noisy, but there are zero logic changes:
()
payloads or just that print "nah"..travis.yml
is already configured to check--no-default-features
, and it passes.I did not make the code warning-clean with
test --no-default-features
, this would (simply!) involve adding morecfg(
everywhere. In my opinion, it is unlikely that it would be possible to move more stuff into the "client" module, to reduce the size of this change. Perhaps the lineproto stuff? Not super relevant.(I'm writing a server-like-thing, if that wasn't obvious.)
Are you willing to carry this feature?