yeah, it's like a list of some of the language features I'm most interested in (probably the only thing really missing from my list would be a form of capabilities- so you can restrict library code to a subset of the capabilities you have- this is because library code is inherently not fully trust worthy, and it's infeasible to thoroughly review all library code).
I think interaction with C code would be important for some of the usecases I'd be interested in, but I wasn't sure if there was anything around that.
It's got an odd feel though - normally languages try to use a small set of deep features to provide many higher level features, but this language feels more like a grab bag than a careful design.
I was also expecting some explanation of how the effects system gets exposed in the type system, but I couldn't find anything in the text about that.
And you're right. A GIL feels very suspect.
Having said all that, the most important part of any programming language is its ecosystem, so more detail on syntax highlighting, refactoring (is there an LSP?) and community (maybe there should be more than just test-package on the official package manager site?) would be welcome.
I think interaction with C code would be important for some of the usecases I'd be interested in, but I wasn't sure if there was anything around that.
It's got an odd feel though - normally languages try to use a small set of deep features to provide many higher level features, but this language feels more like a grab bag than a careful design.
I was also expecting some explanation of how the effects system gets exposed in the type system, but I couldn't find anything in the text about that.
And you're right. A GIL feels very suspect.
Having said all that, the most important part of any programming language is its ecosystem, so more detail on syntax highlighting, refactoring (is there an LSP?) and community (maybe there should be more than just test-package on the official package manager site?) would be welcome.