Skip to content

Conversation

@Techcable
Copy link
Owner

Includes the following Changes:

  • Set up CI
  • Eliminate unnecessary use of serde_derive and bytemuck_derive
  • Miscellaneous documentation improvements
  • Improve error messages for bad feature combos.

The crate cannot function without at least one of the 'nightly' or 'std' features.

The 'unique-wrap-std' implicitly enables the 'std' feature,
but raises an error if the 'nightly' feature is not explicitly be enabled.
The 'nightly' requirement will be dropped if `#[feature(thread_id_value)]` is ever enabled.

Before this change, encountering this issue would trigger a nice `compile_error!`
with a descriptive error message, along with a bunch of other confusing looking errors.
After this change, only the single `compile_error!` is displayed.

This is implemented by adding stub implementations which call `unreachable!()`
Includes the nightly-doc feature, which will show #[doc(cfg(...)] attributes.
All trait implementations are currently manual.
Not needed for something as simple as a newtype.
@Techcable Techcable force-pushed the prepare/0.1-release branch from 4a1c69a to cc50c86 Compare August 30, 2025 02:48
Benchmarks won't compile without it.
In this case it makes things clearer.
Avoids compiling criterion unless necessary, and avoids breaking the MSRV.
@Techcable Techcable force-pushed the prepare/0.1-release branch 2 times, most recently from 0674ed7 to 38b3bfb Compare August 30, 2025 03:12
@Techcable Techcable force-pushed the prepare/0.1-release branch from 38b3bfb to cdba473 Compare August 30, 2025 03:13
First official release.
@Techcable Techcable force-pushed the prepare/0.1-release branch 3 times, most recently from 3a5571d to 6879a25 Compare August 30, 2025 03:29
Avoids an error by cargo-install leading to failed builds
@Techcable Techcable force-pushed the prepare/0.1-release branch from 6879a25 to 949ff7e Compare August 30, 2025 03:30
@Techcable Techcable merged commit 949ff7e into master Aug 30, 2025
30 checks passed
@Techcable Techcable mentioned this pull request Aug 30, 2025
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.

2 participants