What would you do with Compiler as a Service

Question

Seeing that we'll probably get this feature in the next release what are some of the things you either think you'll be able to do or things you would like to use this feature to do?

Personally, during code generation (say in a MSBuild task) I sometimes wish I could grok the code in the project and thus have the option to produce better (more code).

For example, if I have a partial class that has a partial method with a parameter of some type being sent in, then at the time of code generation I could use that information to generate better code.

In other words, I publish my "Intent" at the time of writing code and I could have code generators to the heavy lifting.

partial void InitCommandForStoredProc(ref DbCommand command, string storedProcName);

Given this info in a partial method I could generate the correct code.

So what do you all hope to be able to do with Compiler as a service?

Answer 1

To give (one) practical answer, LINQPad's IntelliSense will benefit immensely from CaaS. It will allow autocompletion to work with both C# and VB (assuming CaaS works for VB, too). It will also make it easy to write cool new refactoring tools.

Give us CaaS, and I'll make LINQPad a showpiece of what you can do with it :)

This feature is far too good to wait until C# 6 / VB 12

Answer 2

Seeing that we'll probably get this feature in the next release

We have not announced scheduling or ship vehicles for any feature or product associated with the "compiler as a service" strategy. CaaS is a long-term forward-looking strategy for how we hope to build compiler architectures in the future. It's not a language feature, it's a strategy for building tools. At the recent PDC Anders did some demos of the sorts of things one might be able to do with such tools, but he specifically did not say when anything like that would ship. You should not expect it any time soon. The only feature we have announced will be in the next release is the asynchronous await feature of C# 5, and we haven't announced a schedule for that either.

what are some of the things you either think you'll be able to do or things you would like to use this feature to do?

Though I am personally very interested in answers to this question, I note that it is not a good candidate for a StackOverflow question. It's vague, speculative and subjective, rather than being about a specific technical coding problem.

Thanks for giving your scenarios though; they are useful to me.

UPDATE: October 2011

We have just shipped a preview release of the "Compiler As A Service" project, aka "Roslyn".

We are still not announcing a ship vehicle; it will be post Visual Studio 11.

Answer 3

I think it would make the weaving process that Aspect Oriented frameworks do, much more powerful. Right now they almost all use some hacky technique that put's requirements on your implementation like inherit from ContextBoundObject, or make all your methods virtual. Having CaaS would make AOP frameworks first class citizens in .NET and I think that would be a huge benefit.

Answer 4

On episode #541 of .NET Rocks!, Anders said the theme of C# 5 will be Compiler as a Service.

Anders Hejlsberg: I could tell you though that one of the things we're working on is this theme and every release has sort of had a theme.

Richard Campbell: Right.

Anders Hejlsberg: In 4.0, you could say the theme is Dynamic, and in 3.0 it was LINQ. The theme for 5.0 is compiler at the service, it's how we're thinking about it

http://www.dotnetrocks.com/text/0541/index12.html

Since April 2010, when this podcast was aired, further announcements at the 2010 PDC indicate the theme will no longer be Compiler as a Service, but instead will be Async programming. No announcements have been made to indicate why a change of theme was required.