News for hackers. Stuff that matters.

A comment on What part of Rust compilation is the bottleneck?. Parent comment

Re:What part of Rust compilation is the bottleneck? by kjksf on Saturday March 16, 2024 @08:16AM (#39725239)
But then you have to compromise on speed of generated code, poor support of windows, number of libraries and overall ecosystem, no ability to generate standalone executables and probably more but I tried OCaml only briefly so can't speak to all of its shortcomings.
[ Parent | on HN ]
Re:What part of Rust compilation is the bottleneck? by pjmlp on Saturday March 16, 2024 @08:24AM (#39725301)
OCaml optimizations are certainly better than Go compiler that hardly does inlining and only recently got some PGO support, and those that care about using LLVM or GCC backends have to compromise on fronteds that still don't do generics.

Go support on Windows is also not great, plugin package doesn't work, filesystem support assumes POSIX semantics, cgo requires installing mingw.

[ Parent | on HN ]
Re:What part of Rust compilation is the bottleneck? by sigsev_251 on Saturday March 16, 2024 @10:24AM (#39726205)
> using LLVM backends

Wait, there is an LLVM based Go toolchain? I thought the Go crowd was known for their NIH obsession.

[ Parent | on HN ]
Re:What part of Rust compilation is the bottleneck? by pjmlp on Saturday March 16, 2024 @11:03AM (#39726536)
TinyGo.
[ Parent | on HN ]