Eliminate the need for extern crate eyra;
#5
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.
Here's a fun trick. If we have Eyra re-export
std
, then users can use it asstd = { package = "eyra", version = "..." }
, which takes over the impliedextern crate std;
, so it gets pulled in without users having to add any extra code to their source files.The result is,
extern crate eyra;
is no longer needed!One downside is that there's no flag to
cargo add
for adding thepackage = "eyra"
part, so it is necessary to add that dependency by hand. On the other hand, it means you don't need to editsrc/main.rs
by hand. Orexamples/*
andtests/*
and so on. So now we're down to just two edits needed to use Eyra.The
extern crate eyra;
approach still works. But overall this new approach seems convenient enough to present it as the default.