Post B6f0K2ZZdnXZowFuOe by solonovamax@tech.lgbt
 (DIR) More posts by solonovamax@tech.lgbt
 (DIR) Post #B6f0K2ZZdnXZowFuOe by solonovamax@tech.lgbt
       0 likes, 0 repeats
       
       why does rust compile literally everything from sourcelike, why not distribute compiled binaries for crates??or if you can't distribute fully compiled binaries due to linking, then distribute like a machine-independent IR that can go through the final compilation step for the target platform
       
 (DIR) Post #B6f0K2sMVwZMlD2ugK by navi@social.vlhl.dev
       1 likes, 0 repeats
       
       @solonovamax they have precompiled static libs in target/**/*.rlib for each projectthe reason we can't ship that or even reuse it across projects, is because rustc refuses to adopt a stable ABI, so an rlib compiled with rustc N may-or-may-not work with rustc N+1 or N-1
       
 (DIR) Post #B6f0K5IJWQW6GHCfPU by solonovamax@tech.lgbt
       0 likes, 0 repeats
       
       like genuinely, I feel introducing an IR would be a rather good idea and wouldn't be too difficult to implementthe IR should probably keep some amount of macro representations for things like macros enabling/disabling code based on the target platform, that way you have only a single IR representation for all targets. but it should expand basically any macro that isn't one of those macros, to make it as easy for the compiler to later consume
       
 (DIR) Post #B6f0MNrfRvAcR2puEK by valk@social.treehouse.systems
       1 likes, 0 repeats
       
       @solonovamax "you can't easily verify a compiled binary" and "the machine-independent IR -> final machine code step is the slow one"