4 ms·
This article, everything else aside, is excellent. I wrote a rambling bunch of stuff in this comment and before I posted I had to cut out a lot, because HN comm
by throwaway17_17 4y ago
This article, everything else aside, is excellent. I wrote a rambling bunch of stuff in this comment and before I posted I had to cut out a lot, because HN comments aren’t really the best place for an in depth discussion about type theory implementations. So, I’m just going to read the compiler source and then get a hold of you later.
I am really intrigued by your explicit anti-features list. They are very close to my preferences for language design, so I was going to keep on reading just from that. The feature list is spelled out well and I certainly think you managed to make this article a nice hook for looking further.
Then I followed a link to the language spec. My god, but is it not only written cleanly, but the presentation is so clean too. I got a short way in (after jumping to the type system specification) and stopped to come comment. I doubt you were expecting to get compliments for layout and formatting, but I am going to shamelessly steal your spec’s presentation for my language docs.
- zetalyrae 4y agoThank you for the kind words! >So, I’m just going to read the compiler source and then get a hold of you later. Luckily, the entire linear type checker is just 600 lines of code: https://github.com/austral/austral/blob/master/lib/LinearityCheck.ml https://github.com/austral/austral/blob/master/lib/Linearity...
- still_grokking 4y ago> Luckily, the entire linear type checker is just 600 lines of code 600 lines of code in an extremely high level and very powerful language. Curious to see it implemented in Austral.