There's a bunch of optional dependencies that are used only for scm-diff-editor.
Binary crates probably want to lock dependencies and use the highest-available version, while library crates probably want to not lock dependencies and use the lowest-admissible version, which results in conflict when trying to run cargo update and decide dependency versions.
People already consider scm-diff-editor as its own separate entity.
It would be a lot easier to install scm-diff-editor if you didn't have to figure out what feature flag you need to pass as part of installation.
Problems:
scm-diff-editor
.cargo update
and decide dependency versions.scm-diff-editor
as its own separate entity.scm-diff-editor
if you didn't have to figure out what feature flag you need to pass as part of installation.