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 cbebdhhd on Wednesday July 06, 2016 @05:07AM (#12041999)

Could you pretty, pretty please allow for an option to have automatic parentheses insertion, similar to how javascript will insert semicolons, making them optional? This is almost exactly the language that I've been planning for the last six months, and if you would be so kind as to implement that one feature, it would save me a lot of reinventing the wheel.

I was originally envisioning having the compiler being able to infer parentheses based on code indentation.

Also have you considered compile time AST evaluation and simplification?

[ Parent | on HN ]

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

If it takes off, and fulfills all peoples' dreams and brings rainbow-farting pink ponies to Earth, then I suppose there might come lots of parser butchering by people and fitting it to their likes via forks/frontends - me, for example, I'd love it to look more Rebol-like ;)

[ Parent | on HN ]

Re:Carp: a statically typed lisp, without a GC, for high per... by larsbrinkhoff on Wednesday July 06, 2016 @07:44AM (#12042435)

Maybe you can use "Readable Lisp S-expressions".

http://readable.sourceforge.net/

[ Parent | on HN ]

Re:Carp: a statically typed lisp, without a GC, for high per... by imtringued on Wednesday July 06, 2016 @07:18AM (#12042356)

If you don't want the parenthesis then why not use reverse polish notation?

[ Parent | on HN ]

Re:Carp: a statically typed lisp, without a GC, for high per... by blastrat on Wednesday July 06, 2016 @08:46AM (#12042674)

unless you're thinking of something that I'm not thinking of? RPN only solves this when the operators are known and used exclusively in operator context and can be relied on as implied close-parens

[ Parent | on HN ]