Philipp Schuster comments

Results 200 comments of


                                            Philipp Schuster

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

I'm developing a bare-metal x86_64 binary, or better to say the initial roottask running under a microkernel. If I have a callstack of `a -> b -> c`, I'd like...

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

btw, I fixed the latest (unrelated) clippy error as well.

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

any update here? @tyranron @JelteF

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

Related issue from 2019: https://github.com/rust-lang/rust/issues/61721

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

Disabling the `simd`-feature doesn't change anything, unfortunately.

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

~In the meantime, I found out that the problem originates in `hashbrown`-dependency.~ ~Not when building the library but when building an executable, that uses it. Minimal example:~ ```rust fn main()...

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

@Hugo4IT the workaround is to either use the crate without the simd-feature and soft-float or to pre-render all characters, such as https://crates.io/crates/noto-sans-mono-bitmap does it

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

@Hugo4IT @mooman219 this is a bug by Rust when using the "+soft-float" feature on x86. more info: https://github.com/rust-lang/rust/issues/62729

use biquad instead of lowpass filter

in upcoming lowpass-filter release, it will say, that `biquad` is a better alternative

Advice/Documentation for final brightness

Thanks @pedrocr ! Wow, parsing RAW files is more complicated than I initially expected Where do you have all the background knowledge from for all the calculations you do? For...