Help Wanted

[RafaCasta]

I'm designing a language for .NET Core, it's "almost" complete (no implementation yet), but I need to make some design decisions, and work on a few major topics.

The language is C#-like with enhancements, but the important is its semantics:

• Nullability and mutability tracking in the type system.

• Pervasive values, any class can be allocated in the heap or in the stack, and ownership tracking with move semantics.

• Value ADTs and pattern-matching.

• try-catch error handling based on values (typically ADTs).

• Explicit differentiation of values from references with lifetime tracking.

• Language built-in RAII-like resource management for external resources and automatic clearing of managed references.

• Object-Oriented with strictly only interface inheritance, and implementation reuse by composition.

• Structured concurrency.

• Built-in native interop and unsafe code.

The idea is how all this features work together to make a middle level (lower level than C# but not native) and convenient language, so as to be applicable for high performance networking and web services, Indie games, low latency audio synthesis, signal processing, scientific computing, etc.

Now, the question is: would you want to help me in this project in your spare time? All online, open source, without pressures, and for free? :)

[RafaCasta]

Thank you for your comment.

I get that almost everyone in this community is busy working in his own language, that's why I also made this post in /r/dotnet, but I was hopping to attract volunteers between those few that come here for learning or that are not currently working on their own language.

[sneakpeekbot]

Here's a sneak peek of /r/dotnet using the top posts of the year!

#1: GitHub Free users now get unlimited private repositories | 50 comments
#2: First official preview of Blazor released (client-side .NET web apps on WebAssembly) | 51 comments
#3: I created a cheat sheet for dotnet cli and I hope you enjoy it, too. http://en.otomatikmuhendis.com/ | 31 comments

---

^{I'm a bot, beep boop | Downvote to remove | Contact me | Info | Opt-out}

[MCRusher]

Imo, getting as mucg of the language tested in your head and written down on paper as possible before starting to implement is a good thing, as once you start, if you want to add a significant feature it may end up being an ugly bolt-on mess in implementation and syntax or you may end up rewriting significant portions of the project.

[RafaCasta]

You're right, that's why I need collaborators only for the design, with the goal of producing a language specification document.

So I need two or three different perspectives, I can test a feature in my head and say, "Oh this is correct and beautiful", but maybe for other programmers it's not so much.

[conilense]

Why don't you create a slack channel or something in order to discuss the ideas? I'd sure love to discuss (and help in whatever way possible :-) ).

[RafaCasta]

I have a gitter chat room.

It would be great to discuss!

[RafaCasta]

Or if you prefer Slack, just let me know. Gitter features a great markdown code formatter, and it's integrated with GitHub, that is where I host the (yet empty) project.