Matthias Krüger

There's probably a problem when we try to remove a waypoint that is referenced to (has a connection) by another waypoint.

Hmm, I can see that in both case, `kondo` and `kondo .` inside $HOME, `prepare_directories` returns the same path `/home/matthias` ```` ~/vcs/github/kondo/target/debug/kondo [kondo/src/main.rs:34] Ok(vec![cd]) = Ok( [ "/home/matthias", ], )...

Mmh, it seems that in both cases, `project_artifact_bytes` is actually zero, so we enter the "continue" and don't do any cleaning at all :thinking: ```` [kondo/src/main.rs:85] project_artifact_bytes == 0 =...

Oooh! ```` [kondo/src/main.rs:37] dirs.into_iter().map(|d| path_canonicalise(&cd, d)).collect() = Ok( [ "/home/matthias", ], ) [kondo/src/main.rs:64] p.ok() = Some( Project { project_type: Node, path: "/home/matthias", }, ) [kondo/src/main.rs:67] &project = Project { project_type:...

So I have not tried this, but you can probably also confuse kondo by adding something like a `Cargo.toml` into your home and then running `kondo ~` which might also...

I guess we could treat directories that we get passed explicitly such as `.`, `~`, `some/path/` special and still walk them recursively BUT also print a warning at the same...

Its removed from the r+ queue now. The queue does not update in realtime apparently :upside_down_face:

triage: it seems the `let_chains` feature has not been stabilized yet.

no tests?

Another example ````rust fn main() { let handle = core::thread::spawn(|| {}); assert_eq!(SHARED.fetch_addAtomicUsize::new, 1); } ````