dabrahams

4 ms·

1. 1.▲
   by dabrahams 4y ago

   It should work fine on other platforms supported by Swift (Windows, Linux, …) but hasn't been tested there. And yes, pretty useless to everyone at this stage; it's a work in progress.
2. 2.▲
   by dabrahams 4y ago

   We've been using the word "binding" in our more formal work (see the specification repo, which is more up-to-date than the README), and having clarified that for ourselves, we will probably stop talking about "immutable
3. 3.▲
   by dabrahams 4y ago

   At this stage it is definitely a research language. We're very aware that new languages come along every week and die in obscurity, and the lift to make one successful is huge. That said, I have to admit it's very hard for us to k
4. 4.▲
   by dabrahams 4y ago

   Memory safety is guaranteed in the safe subset of the language, and we plan to use a naming convention to mark unsafe constructs, like in Swift. One notable difference: pointers are not unsafe; only their dereference operation is.