Split off messages
function into their own trait
#55
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.
Issue: #53
Description
This PR splits of the
messages()
function of theBackendHandle
trait into its ownBackendHandleMessages
trait. This removes the previously used feature, and ensures theBackendHandle
trait is always object safe.Motivation
Previously, a cargo bug would union all features of a crate in the dependency tree. This means that
cargo COMMAND
would fail becausegenealogos-api
required theBackendHandle
to be object safe, andgenealogos-cli
required theBackendHandle
trait to implement themessages()
function.As a result,
cargo dist
,cargo build
,rust-analyzer
, and many other commands would fail. This PR resolves that issue.Checklist
Checklist before merging: