Iron(III) Oxide

> Instead of a lock-free allocator, which is likely impossible, why is lock-free allocator likely impossible? > Heap allocations are horribly expensive right now because the Heap acquires an Irq-safe...

The following lints are solved now: * [x] char_lit_as_u8 * [x] manual_flatten * [x] assign_op_pattern * [x] collapsible_else_if * [x] collapsible_if * [x] collapsible_match * [x] comparison_to_empty * [x] println_empty_string...

I don't think this issue is finished yet. There are more lints that need to be fixed. I'll be working on it and send more PR:s in the coming future

These ones: $ cargo clippy ``` warning: redundant pattern matching, consider using `is_some()` --> kernel/frame_allocator/src/lib.rs:130:32 | 130 | if let Some(_) = current.overlap(other) { | -------^^^^^^^------------------------- help: try this: `if...

> you can get a library function into std faster through the ACP process https://std-dev-guide.rust-lang.org/development/feature-lifecycle.html#suitability-for-the-standard-library. > > anyway what is the use case for this not covered by `format!("{:.2}", full_float)`?...

 the bug has been partially solved but there's another related issue where clicking on the blank line after a paragraph makes the cursor jump back up. See screenshot. Here's...

I don't know why the lint thinks that "multithreading" isn't a valid word. Perhaps add to dictionary?

I gotta start somewhere. I think a good place to start is to stop interpreting : and after as part of filename in CLI arguments. If it looks good so...

is it good now?

I applied feedback. Looking forward to next feedback round!