Daniel Huang

The current implementation is quite inefficient, as it requires an allocation on each call. Criticism is welcome.

WIP: Fix particle decay

7

Closes #34 Still needs additional testing and/or tweaking.

The npm package `querystring` depends on `phantomify` `~0.x.0`. Parsing this results in a panic. #9 before merging (3af6c068bc59f58683a536cbcf683c5cec69621f) did not panic.

Fix system lag on copy (WIP)

3

Not yet fully tested, should fix #428

Refactor noise processing

5

The current implementation (dropping samples and introducing a delay) tends to introduce a delay which doesn't get reduced even after CPU load is reduced and processing is able to keep...

Fix long type paths by breaking paths into multiple lines when exceeding maximum width

2

A long type path could look like `long_type_path::long_type_path::long_type_path::long_type_path::long_type_path::long_type_path::long_type_path::long_type_path::long_type_path::long_type_path::Long` which currently would not get formatted. This fix would break the path into multiple lines if necessary.

Referred from https://github.com/rust-lang/rustfmt/pull/6494 A long type path could look like `long_type_path::long_type_path::long_type_path::long_type_path::long_type_path::long_type_path::long_type_path::long_type_path::long_type_path::long_type_path::Long` which currently would not get formatted, but this could exceed rustfmt's `max_width` setting. How could this be handled?