Kyle J Strand
Kyle J Strand
I think I may have found a better solution. Launching wsl using `wsl.exe` instead of `bash.exe` lets you specify that the shell should start in the home directory, and presumably...
Hm... not sure how to fix the links to the newly-introduced page. Is there an index page I need to edit? Edit: I think I found it
Hm...the `panic` information in `runtime.md` should be edited as well.
I was going to open a new bug report about this, but I've found that `git status` slows down the Starship prompt quite a bit even in WSL 2, but...
@romkatv Are you using Windows' native `git` with those repos, or a WSL `git`?
....actually, if `starship` can detect a native version of Git and use it on NTFS, that would be even slicker.
Isn't WSL git on NTFS slow even outside the context of `starship`?
[This PR](https://github.com/rust-lang/rust/pull/65646) should ensure that `catch_unwind` does not catch C++ exceptions _or_ forced-unwinding. @Amanieu I can't remember; was an abort for foreign exceptions in `catch_unwind` introduced after that?
...ah. Indeed it was: https://github.com/rust-lang/rust/pull/70212/ From the description, it does sound to me like removing the `catch_unwind` is the right long-term strategy, since the intent is merely to avoid UB....
Actually, I believe that with `panic=abort`, you can safely use `"C-unwind"` everywhere, which will guarantee that both Rust `panic` and foreign unwinding (including the `pthread_exit` case here) will safely `abort`....