Roslyn and a .NET less C#? [closed]

Question

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.

Closed 9 years ago.

Roslyn is written in C# with some initial bootstrapping. Does it pave the way for a day when we don't need .NET for c#? Maybe a version of C# with a ".NET" runtime that is so small that we do not even consider it ".NET"?

Thanks in advance for your assistance.

Answer 1

Roslyn is written in C# with some initial bootstrapping. Does it pave the way for a day when we don't need .NET for c#?

I note that StackOverflow is not a good place to ask questions that require predictions of the future. I'll therefore confine my remarks to the present.

The purpose of the Roslyn project is to make it easier for people to do lexical, syntactic and semantic analysis of C# and VB programs. If you want to use the Roslyn lexical, syntactic or semantic analyzers to make a compiler that compiles C# for some other runtime, I suppose you could do that, but that's not one of our key scenarios for the project. We expect that most people will be using Roslyn to do analysis of programs that run on .NET.