Explore removing SmallVec
from Event
enum
#614
Merged
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 explores removing the dependency on
smallvec
and replacing it withVec
fromstd
.smallvec
is a third party dependency that leaks into the public API. If applications that depend onrustyline
wish to create custom key bindings, they must also depend onsmallvec
to constructEvent::KeySeq
.This PR replaces
smallvec
, which is a complicated data structure with lots of unsafe code and several known security advisories, with a vocabulary type fromstd
.This has the effect of reducing the size of the
Event
enum.Because
Event
is a public enum, changing the type of the field inEvent::KeySeq
is a breaking change. I've shown this change in the sequence of commits in this branch and the addition of a test.Motivation of this PR is reducing dependencies.
@gwenn if you'd prefer, I'd be willing to try an alternate PR that conditionally enables
smallvec
with a Cargo feature. I think it looks easy enough to support.