The Lobster Programming Language

Re:The Lobster Programming Language by steveklabnik on Wednesday April 03, 2019 @06:10PM (#19567674)

A comparison to Swift's ARC would also be of interest :)

[ Parent | on HN ]

Re:The Lobster Programming Language by Aardappel on Tuesday April 16, 2019 @08:02PM (#19678457)

http://aardappel.github.io/lobster/memory_management.html

[ Parent | on HN ]

Re:The Lobster Programming Language by Aardappel on Wednesday April 03, 2019 @06:29PM (#19567776)

Yup, I will write up the algorithm some time soon.

I've seen Swift's intentions to add lifetime analysis to ARC, but from what I could see it is much more complicated in Swift, requires annotations, and with significant runtime overhead remaining.

[ Parent | on HN ]

Re:The Lobster Programming Language by steveklabnik on Wednesday April 03, 2019 @06:31PM (#19567784)

Arc isn’t that stuff, Arc is what it already does today. “Automatic reference counting.”

[ Parent | on HN ]

Re:The Lobster Programming Language by Aardappel on Wednesday April 03, 2019 @06:39PM (#19567822)

I'm aware of that, I said "add lifetime analysis to ARC", as in, ARC is what I call regular runtime reference counting, and with lifetime analysis some of it can move to compile time.

[ Parent | on HN ]

Re:The Lobster Programming Language by steveklabnik on Wednesday April 03, 2019 @06:42PM (#19567843)

Yep oops, sorry.

Anyway, psyched to see more people experimenting with this kind of thing!

[ Parent | on HN ]

Re:The Lobster Programming Language by Aardappel on Wednesday April 03, 2019 @07:57PM (#19568246)

Yes, I frankly feel this design space is the future of memory management. GC, begone!

[ Parent | on HN ]

Re:The Lobster Programming Language by alexisread on Thursday April 04, 2019 @06:42AM (#19570752)

http://concurrency.ch/Content/publications/Blaeser_Component...

This seems to scale out very well - it's kind of static GC analysis with RAII and erlang-style messaging.

[ Parent | on HN ]