Ensure that SHA2 and SHA3 crates are #![no_std]

Open
#71 0 comments 0 reactions 1 assignee View on GitHub

@jjkurczak is already working on this.

Since Aug 10, 2026.

Assessment

This issue has not been assessed yet.

Description

Summary:

The purpose of this sub-issue is to implement sufficient no_std changes such that SHA2 and SHA3 crates are able to be built, tested, and benchmarked in no_std.

Scope:

The expected changes for this initial task may involve changes to other crates, and the workspace, to support required changes to crate dependencies, and to create a baseline for all crates to implement the new functionality uniformly.

Acceptance Criteria:
  • A new feature will be added that positively enables std, which will be on by default
  • the --no-default-features flag will be used to enforce no_std at build time
  • SHA2 and SHA3 crates must build/test/bench, individually, with --no-default-features
  • All crates must continue to build/test/bench, with no regressions, in default config.
  • Building other crates or the entire workspace with --no-default-features is unsupported, with no required behavior associated with acceptance of this sub-issue
Dominant language
Rust
Stars
25
Forks
18
Avg merge
16h 38m
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bcgit/bc-rust

All issues in bcgit/bc-rust

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.