Coalton: How to Have Our (Typed) Cake and (Safely) Eat It Too, in Common Lisp

Re:Coalton: How to Have Our (Typed) Cake and (Safely) Eat It... by nyanpasu64 on Saturday September 11, 2021 @12:23AM (#28489418)

Not really related to the type system and bridging, but can the compiled code run in real-time without interference by the garbage collector? Can you define an entire thread running statically typed code which never gets interrupted by the garbage collector? C# definitely can't do the latter.

Or am I confusing "statically typed" and "no GC"? Sadly a lot of even statically-typed languages lack support for transparently bridging between application and no-GC real-time code, using the same data types on both sides. I'd be fine writing application code in a no-GC language, but it seems most GUI libraries are sadly for GC languages.

[ Parent | on HN ]

Re:Coalton: How to Have Our (Typed) Cake and (Safely) Eat It... by Smaug123 on Saturday September 11, 2021 @04:07AM (#28490256)

"Statically typed" means roughly that variables have known types at compile time, for whatever the word "type" means in your chosen language. "No GC" means, well, that there is no runtime entity that manages memory cleanup for you. They are totally unrelated.

[ Parent | on HN ]

Re:Coalton: How to Have Our (Typed) Cake and (Safely) Eat It... by reikonomusha on Saturday September 11, 2021 @02:28AM (#28489829)

They’re different concepts. Statically typed doesn’t mean that lifetimes are determined statically.

[ Parent | on HN ]