Carp: a statically typed lisp, without a GC, for high performance applications

Re:Carp: a statically typed lisp, without a GC, for high per... by eriksvedang on Wednesday July 06, 2016 @11:05AM (#12043525)

Thanks for the links!

The short answer is that safety is handled similar to Rust, using lifetime analysis. It's quite a bit more simplistic than Rust at the moment though. Also, some checks are done at runtime (like bounds checking on arrays, when turned on).

[ Parent | on HN ]

Re:Carp: a statically typed lisp, without a GC, for high per... by rurban on Wednesday July 06, 2016 @12:41PM (#12044246)

Using the information on dependent types and some inference and eliminate run-time type checks in those cases would be a nice type-checker job, e.g. for the sicp/solver.

[ Parent | on HN ]

Re:Carp: a statically typed lisp, without a GC, for high per... by nickpsecurity on Wednesday July 06, 2016 @02:11PM (#12044845)

Ok. There we go. It's actually what I had in mind for PreScheme. You just gave me more confidence in it.

[ Parent | on HN ]