[necubi]

I'm mostly suggesting that if you implicitly claim to have solved some huge, difficult research problem but provide no real details about how, people are going to be skeptical. This doesn't have to mean a formal research paper. Even one page on your website describing your approach (potentially with comparisons to other state-of-the-art languages like Swift, Rust, and Koka) would be helpful for potential users trying to understand your language's capabilities.

Just as some basic questions you might want to answer:

1. If I allocate some memory and store a reference to it in a struct or object, how do you track ownership for that memory? Can I alias it? Store references to it in multiple structs? How do you know that it's safe to free that memory without reference counting?

2. Am I allowed to allocate memory in a function and return a reference to that memory? How do you ensure that memory lives long enough for those references to be valid?

3. Are multiple aliases allowed to overlap with each other? If so, how do you prevent (e.g.,) type confusion from one mutiple alias changing the data out from under the other?

[levodelellis]

> if you implicitly claim to have solved some huge, difficult research problem but provide no real details

You do realize you can download the compiler and confirm for yourself that it's all working right this very moment?

There's probably a few aliasing bugs since I add new features. types and haven't tried to break my code or find difficult to run into bugs