Skip to content

fix(dasp_signal): make boxed feature actually build the intended module - #2

Closed
AlexTMjugador wants to merge 2 commits into
masterfrom
fix/dasp-signal-no-std-build
Closed

AlexTMjugador wants to merge 2 commits into
masterfrom
fix/dasp-signal-no-std-build

Conversation

@AlexTMjugador

Copy link
Copy Markdown
Member

While working on RustAudio#204, a relatively recently-introduced compiler warning about features not being a recognized cfg condition name caught my attention. After taking a look at the underlying code, I realized that it had the consequence of rendering the boxed feature of dasp_signal non-functional, since it always evaluated to false and thus the boxed module containing a Signal implementation for boxed signals was not compiled in.

To fix that, these changes correct the identified cfg typo.


Stack created with GitHub Stacks CLI • Give Feedback 💬

…htlies

Rust PR rust-lang/rust#160989, which is already
part of the latest 1.100 nightlies, changed several unstable
`core::intrinsics` functions to be generic, which implied a breaking
name change. Unfortunately, these are used by `dasp_signal` when the
`std` feature is not enabled.

These changes make `dasp_signal` use the new intrinsic names, so that
builds without the `std` feature work again on the latest nightlies.
People that have to keep using older nightlies for any reason may
temporarily pin their dependency on `dasp_signal` to a version
compatible with their nightly build.

While at it, I have also realized that such intrinsics have not been
unsafe for a while now, so I removed their surrounding `unsafe` blocks.
@AlexTMjugador
AlexTMjugador added this pull request to stack #3 September 27, 2026 14:08
@AlexTMjugador
AlexTMjugador removed this pull request from stack #3 September 27, 2026 14:11
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