silt!

> @siltyy I'm afraid I'm the bearer of an even more soul-shattering epiphany: it's pronunciation. You have out-pedantried me, and for this, I salute you.

i figured out how to get this working, here's the relevant segment of my `config.toml` ```toml [build] target = "riscv64gc-unknown-none-elf" rustflags = [ "-Clinker=clang", # use clang instead of rust-lld...

Is this still an issue for you? Running into it rn, also on Android 14 (specifically GrapheneOS on the off chance that it matters). Aliucord's debug logs also end up...

Well that's.. interesting. I tried toggling exploit protection compatibility mode, but that didn't fix it. No clue what else could be behind this O.o

UNIX-like file paths, on Windows? I'm a bit confused about what you mean, since I've also tried stuff like `/tmp/socket`, `/z/tmp/socket`, `\\?\GlobalRoot\Global??\Z:\tmp\socket`, `\\?\Global\Z:\tmp\socket`, and even just `\socket` and `/socket` with...

https://github.com/haraldh/rust_uds_windows/blob/fb5e294a1c7430cfacc19e8fad6332a1abb33a95/src/stdnet/mod.rs#L55 `Z:\tmp\socket`, `z:\tmp\socket`, and (with the socket in `C:`'s root) `\socket` are all valid Win32 file paths as defined by https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file and should work assuming the comment is correct and...