Skip to content

Conversation

rodrimati1992
Copy link
Owner

@rodrimati1992 rodrimati1992 commented Oct 30, 2024

This PR is blocked on the Rust 1.83.0 release, and &mut in const not being unstabilized while that Rust version is in beta.

Updated all uses of "mut_refs" and "nightly_mut_refs" features,
now neither is mentioned in the docs,
functions are now const conditional on the `"rust_1_83"` feature,
and "nightly_mut_refs" no longer enables the "const_mut_refs" feature
(because it's no longer necessary to use &mut in const).

Updated github CI config

Updated docsrs feature config
…dding

the padding went frmo `TypeNe<(), ()>` to `TypeEq<(), ()>`

By using `TypeEq` as trailing padding,
it makes it so that `SomeTypeArgIsNe::TRY_NEW` doesn't construct
a `SomeTypeArgIsNe` when the only `TypeNe` is a padding `TypeNe<(), ()>`,
which currently doesn't lead to soundness bugs but might have led to
future ones if not fixed.
- is_true
- is_false
- to_true
- to_false
- unwrap_true
- unwrap_false

Added tests for these methods

Relaxed `Copy + Clone + Debug` impls of `BooleanWitG` to work for any
`<B> BooleanWitG<B>`, instead of requirning `<const B: bool> BoolWitG<Bool<B>>`.

Updated what non-proc_macro UI tests output

Updated changelog
@rodrimati1992 rodrimati1992 changed the title 1.10.0 release 1.11.0 release Dec 4, 2024
@rodrimati1992 rodrimati1992 merged commit 3e0d052 into main Dec 4, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant