Philipp Schuster

Doesn't build in no_std env but it seems like it is supposed to build there

4

I wanted to use this library in a `no_std` environment, but it doesn't compile because of the `miniz_oxide` crate. If I see it correctly in `Cargo.toml` and `lib.rs`, this crate...

display: enum match arms: use 'Self' (to fix incompatibility with `#![deny(clippy::use_self)]`

6

This PR makes the generated code compatible with a global setting of `#![deny(clippy::use_self)]` by using `Self::Variant` instead of `EnumName::Variant`.

wrong download path for Node 10 on arm7l-Architecture (Rasbperry Pi 3) (no more x86 binaries)

5

Hi! Since Node 10 NodeJs.org doesn't provide binaries for (linux) x86 anymore. Frontend-Maven-Plugin tries to download `https://nodejs.org/dist/v10.0.0/node-v10.0.0-linux-x86.tar.gz` on my Rasbperry Pi 3 (with Rasbian Operating System) which is not there...

add no_std-support

1

Hi! If you accept this PR and release it, `no_std`-crates can use this as dependency. Otherwise they don't compile. You can verify this with these commands: - `$ rustup target...

Doesn't compile with "+soft-float": Compiler LLVM Error: "Do not know how to split the result of this operator"

10

This is probably a bug in the Rust compiler but maybe this can be easily fixed by a workaround or someone already has experience with this error? When this crate...

This only focuses on changes I have locally (big refactoring). I figured out that I can dramatically (50+%) reduce the calculation overhead of the bandpass filters if each bandpass filter...

- [x] no_std in code - [ ] make sure to tell users in README about it

use the knowledge I gained recently and improve the implementation (e.g. dynamic audio input stream configuration)

My lowpass filter is finally "good enough" and yet simple. Well-enough results