The idea to what thins language aims to be seems to be all around in old conversations/issues. I'd like to summarize it in a short list here. It begins with the README bullets, but will expand further.
A generally high-level language with the aim to replace C# (do to C#, what Kotlin did to Java)
Keeping the good aspects of C#
Strongly and statically typed
Not an academic/research language, something that's usable by the average .NET developer
Readable by people coming from other languages
Great debugging
Great editor support
Starting to embrace a more functional-style way of programming (LINQ, pattern matching, ...)
It prefers generalized approaches over sugared special cases
It adds a bigger and more worked out feature earlier, than an underspecified one that will result in extra features to work out the missed use cases
Keeping C# interop as long as we are not sacrificing too much for it. If we need to give up either a great feature or complicate our interop layer, possibly do the latter. If we need to, we can help the interop layer from the C# side with analyzers + metadata.
The idea to what thins language aims to be seems to be all around in old conversations/issues. I'd like to summarize it in a short list here. It begins with the README bullets, but will expand further.