fix: make several crates build again without std on the latest nightlies - #204
Open
AlexTMjugador wants to merge 2 commits into
Open
AlexTMjugador wants to merge 2 commits into
AlexTMjugador wants to merge 2 commits into
Conversation
…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.
Contributor
Author
|
I see that some CI workflows are failing due to similar upstream changes in intrinsics other crates in the workspace depend upon. I'll expand the scope of this PR to address those as well, since otherwise there doesn't seem to be a clean way to get it merged. |
AlexTMjugador
changed the title
std on the latest nightliesstd on the latest nightlies
This was referenced Sep 27, 2026
Closed
AlexTMjugador
added a commit
to ComunidadAylas/dasp
that referenced
this pull request
Sep 27, 2026
…dule 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.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rust PR rust-lang/rust#160989, which is already part of the latest 1.100 nightlies, changed several unstable
core::intrinsicsfunctions to be generic, which implied a breaking name change. Unfortunately, these are used bydasp_signalwhen thestdfeature is not enabled.These changes make
dasp_signaluse the new intrinsic names, so that builds without thestdfeature work again on the latest nightlies. People that have to keep using older nightlies for any reason may temporarily pin their dependency ondasp_signalto 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
unsafeblocks.