News for hackers. Stuff that matters.
Re:The Swift compiler is slow due to how types are inferred by lolinder on Wednesday June 12, 2024 @03:57PM (#40662349)
> Nothing breaks my flow like waiting for compilation. With a sufficiently fast compiler (and Go is not fast enough for me), you can run it on every keystroke and get realtime feedback on your code.

I already get fast feedback on my code inlined in my editor, and for most languages it only takes 1-2 seconds after I finish typing to update (much longer for Rust, of course). I've never personally found that those 1-2 seconds are a barrier, since I type way faster than I can think anyway.

By the time I've finished typing and am ready to evaluate what I've written, the error highlighting has already popped up letting me know what's wrong.

Re:The Swift compiler is slow due to how types are inferred by TillE on Wednesday June 12, 2024 @04:06PM (#40662460)
Yeah even with a large C++ codebase, any decent IDE will flag errors very quickly in real time. I dunno, I've never found that waiting a minute to run a test or whatever is particularly detrimental to my workflow.

I understand the benefits of super fast iteration if you're tweaking a GUI layout or something, but for the most part I'd prioritize many many other features first.

Re:The Swift compiler is slow due to how types are inferred by hu3 on Wednesday June 12, 2024 @04:26PM (#40662701)
Fast compilation + unit tests allows me to quickly check if I broke a lot more stuff than IDE local checks.