Skip to content

[pull] master from RustCrypto:master #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 955 commits into
base: master
Choose a base branch
from

Conversation

pull[bot]
Copy link

@pull pull bot commented Jul 30, 2019

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

dependabot bot and others added 22 commits March 25, 2023 16:12
Bumps [proc-macro2](https://github.com/dtolnay/proc-macro2) from 1.0.52 to 1.0.53.
- [Release notes](https://github.com/dtolnay/proc-macro2/releases)
- [Commits](dtolnay/proc-macro2@1.0.52...1.0.53)

---
updated-dependencies:
- dependency-name: proc-macro2
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
This makes it easier to implement the `Cmov` trait for foreign types.

It additionally makes the `value` argument an `&Self` reference, which
should make it easier to impl the trait for non-`Copy` types where it's
desirable to avoid a move.

Note: breaking change
Adds PPC32, which should be useful for checking that any optional
ASM-based features will still work on platforms where ASM has not yet
been stabilized.
Bumps [proc-macro2](https://github.com/dtolnay/proc-macro2) from 1.0.53 to 1.0.54.
- [Release notes](https://github.com/dtolnay/proc-macro2/releases)
- [Commits](dtolnay/proc-macro2@1.0.53...1.0.54)

---
updated-dependencies:
- dependency-name: proc-macro2
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [generic-array](https://github.com/fizyk20/generic-array) from 0.14.6 to 0.14.7.
- [Release notes](https://github.com/fizyk20/generic-array/releases)
- [Changelog](https://github.com/fizyk20/generic-array/blob/master/CHANGELOG.md)
- [Commits](https://github.com/fizyk20/generic-array/commits)

---
updated-dependencies:
- dependency-name: generic-array
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
The where clauses I was previously injecting *were* load bearing, but
they needed to be filtered for skipped fields.

Fixes #878
Adds support for extracting secp224r1 test vectors from Wycheproof, in
order to test the `p224` crate.
This fixes compilation of dependent crates for these targets.

For example, `sha2`:

Before:
```
$ cargo build --target x86_64-unknown-none --no-default-features
   Compiling sha2 v0.10.6 (/home/rvolosatovs/src/github.com/rustcrypto/hashes/sha2)
LLVM ERROR: Do not know how to split the result of this operator!

error: could not compile `sha2`
$ cargo build --target x86_64-unknown-uefi --no-default-features
   Compiling sha2 v0.10.6 (/home/rvolosatovs/src/github.com/rustcrypto/hashes/sha2)
LLVM ERROR: Do not know how to split the result of this operator!

error: could not compile `sha2`
```

After:
```
$ cargo build --target x86_64-unknown-none --no-default-features
   Compiling cpufeatures v0.2.5 (/home/rvolosatovs/src/github.com/rustcrypto/utils/cpufeatures)
   Compiling sha2 v0.10.6 (/home/rvolosatovs/src/github.com/rustcrypto/hashes/sha2)
    Finished dev [optimized + debuginfo] target(s) in 0.19s
$ cargo build --target x86_64-unknown-uefi --no-default-features
   Compiling cpufeatures v0.2.5 (/home/rvolosatovs/src/github.com/rustcrypto/utils/cpufeatures)
   Compiling sha2 v0.10.6 (/home/rvolosatovs/src/github.com/rustcrypto/hashes/sha2)
    Finished dev [optimized + debuginfo] target(s) in 0.19s
```

Signed-off-by: Roman Volosatovs <[email protected]>
newpavlov and others added 22 commits February 24, 2025 14:50
#1166)

The workaround is no longer needed since we have bumped MSRV to 1.85.
The methods can be useful in cases where we want to support `inout`
APIs, but algorithm implementation supports only the in-place mode.
When clippy runs without `block-padding`, it will throw warnings:
```
warning: the following explicit lifetimes could be elided: 'inp, 'out
   --> inout/src/reserved.rs:152:6
    |
152 | impl<'inp, 'out> InOutBufReserved<'inp, 'out, u8> {
    |      ^^^^  ^^^^                   ^^^^  ^^^^
    |
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_lifetimes
    = note: `#[warn(clippy::needless_lifetimes)]` on by default
help: elide the lifetimes
    |
152 - impl<'inp, 'out> InOutBufReserved<'inp, 'out, u8> {
152 + impl InOutBufReserved<'_, '_, u8> {
```
This crate contains `std::io`-compatibility wrappers which are moved
from the `digest` crate.
Fixes badges in the crate README and moves hash crates used in examples
to dev dependencies.
Fixes the `clippy::ptr_eq` lint.
This PR should make it a bit easier for new users to create blb files
and to inspect the existing ones.
The `minimal-versions` job was missing the `uses` key
The generated code is *almost* `const fn` friendly with `const_mut_refs`
but needs `const fn` accessors for the newtypes it defines:

mit-plv/fiat-crypto#1955

This updates `fiat-constify` to solve only adding such accessors and
annotating the functions as `const fn`, greatly reducing its scope and
making the resulting postprocessed code much closer to the original
generated code.

Additionally it removes the extra methods added to the code, namely
`as_inner` and `into_inner`, in order to ensure that the output is as
close to the original generated code as possible.
Also adds `publish = "false"` as this tool is not intended for release
(ideally we can eventually get rid of it), but the version bump denotes
a major notable change to the codegen
This is useful for `-Z minimal-versions` to ensure derived code builds
without warnings on recent Rust versions, which complain about the
earlier custom derive:

```
error: non-local `impl` definition, `impl` blocks should be written at the same level as their item
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⤵️ pull merge-conflict Resolve conflicts manually
Projects
None yet
Development

Successfully merging this pull request may close these issues.