-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Initial steps toward making
std
an optional feature. (#81)
* feat: change some imports from std to core As part of #20, we'd like to make `std` into an optional dependency for the `gitoid` crate, so it can be used in `no_std` environments. This requires both transitioning usage of dependencies to `no_std`, and moving our own imports away from `std`. As a first step, this commit transitions just the imports which are direct re-exports of things from `core`, to use the original `core` imports instead. We're not ready for `no_std` yet, but this does move us closer. * feat: start move to no_std deps Per #20, we want to make `gitoid` `no_std`-compatible. Three of our deps: `hex`, `sha1`, and `sha2` are `no_std`-compatible. Of those, only `sha2` appears to be able to transition to turn off `std` immediately without impact to the APIs we use. For `hex` and `sha1`, we'll need to update our usage of the APIs to avoid the things that are turned off when the import becomes `no_std`. This commit doesn't undertake the work of actually transitioning the usage, but _does_ update the `Cargo.toml` file to: - Transition `sha2` to `no_std` immediately. - Update our import of `hex` and `sha1` to turn off default features and then purposefully activate the `std` feature. This makes the status of using `std` more clear, and paves for way for removing the manual activation in the future when we've updated our usage of those deps. Signed-off-by: Andrew Lilley Brinker <[email protected]>
- Loading branch information
1 parent
8d88434
commit 8d790c7
Showing
9 changed files
with
34 additions
and
31 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters