News for hackers. Stuff that matters.
Re:My ideal Rust workflow by yakubin on Wednesday October 27, 2021 @09:13AM (#29012860)
> I can see the frustration coming from Lisp, but it's just business as usual in compiled, strongly typed system languages.

Not really. SML and OCaml let you evaluate selected code snippets in REPL just fine, and their compilation is fast. I'm not sure about Haskell, but I'd guess it's similar with ghci.

"Strongly-typed" is in the eye of the beholder, but the phrase "compiled, strongly-typed programming languages" generally doesn't bring to my mind C++ and Java of which this statement would be more accurate.

Re:My ideal Rust workflow by snicker7 on Wednesday October 27, 2021 @09:37AM (#29013131)
People confuse strong typing with static typing all the time. I guess this was the case here.
Re:My ideal Rust workflow by simias on Wednesday October 27, 2021 @10:48AM (#29014004)
I did do that, I feel ashamed.
Re:My ideal Rust workflow by yakubin on Wednesday October 27, 2021 @05:06PM (#29019144)
That's a good one. Brought a smile on my face.

From "What We Do In The Shadows": <https://youtu.be/yy4CN9DVPII?t=85>

Re:My ideal Rust workflow by MrBuddyCasino on Wednesday October 27, 2021 @11:50AM (#29014919)
Java IDEs let you evaluate random code fragments at runtime in the context of the current debugger stackframe. You can also change method bodies (not signatures) and have them hot-reload.

It might look like C++, but the JVM is really more like Smalltalk in nature.

Re:My ideal Rust workflow by Zababa on Wednesday October 27, 2021 @09:54AM (#29013304)
Haskell is relatively slow to compile when compared to OCaml.