Skip to content

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

Open
AlexTMjugador wants to merge 1 commit into
RustAudio:masterfrom
ComunidadAylas:fix/useless-dasp-signal-boxed-feature
Open

AlexTMjugador wants to merge 1 commit into
RustAudio:masterfrom
ComunidadAylas:fix/useless-dasp-signal-boxed-feature

Conversation

@AlexTMjugador

Copy link
Copy Markdown
Contributor

While working on #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.

…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.
@AlexTMjugador

AlexTMjugador commented Sep 27, 2026 •

Copy link
Copy Markdown
Contributor Author

I tried to stack this PR on top of #204 using the new GitHub stacked pull requests feature, but that failed spectacularly: the gh CLI first picked the wrong repository for creating stacked PRs, and then it failed with a strange permissions error when I tried to force it to use the proper upstream remote.

These newfangled, slop-coded, churned-out features are truly a sight to behold, especially when considering that e.g. GitLab has had a working, much simpler stacked merge requests feature for years, which works automagically as long as an MR branch is based on another MR branch... 😅

Anyway, that means I ended up cherry-picking the specific commit for this PR on top of master, so CI will fail until it is rebased on top of the previous PR.

This branch has not been deployed

No deployments
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