If this project can maintain Go's fast compile times and ability to make reliable, concice binaries, those would be two big pluses in areas where Julia is currently weak. That would make this a good choice in projects where those are high priorities.
I find Rust's borrow checker too clunky for exploratory work. It breaks my flow and imposes higher cognitive load. The slow compiler doesn't help either.
That is fair. I have not done enough exploratory work in Rust to comment. Maybe there are abalysis patterns that can avoid bumping up against the borrow checker.
I tend to think the innately slow compiler is basically a fatal mistake. Rust will never be able to be used for large projects. It's not so obvious now because everything it's used for is tiny.
What supports that statement exactly? If you split your big projects into crates it would recompile pretty fast. C++ can also take ages to compile (eg. compiling Firefox from scratch). Keeping your code modular to get decent compile times seems like a win win.