With the recent release (and open sourcing) of the Roslyn compiler for the .NET framework, I’ve started thinking about how it might be constructively used. The powers at Microsoft have made it clear that they won’t be putting the syntax of C# itself up for grabs - and for good reason.
None the less …
… there are some sparkling possibilities - and here are my thoughts on some of them.
await keywords were introduced in C# 5, one of the reasons the C# language team took that particular approach was to use an “opt-in” approach, so that existing code wouldn’t be adversely affected by the new capabilities.
Building on this idea, what if we were able to build in some kind of transactional support into the language thusly:
If we wanted to make this happen, leveraging the Rosylin toolset, perhaps it might look like this:
Points of interest …
[LanguageKeyword]attribute used to specify the keyword required on the method declaration to bring in this particular method extension
MethodExtensionwould be some kind of required base class that provides supporting infrastructure.
[LanguageExtension]attribute identifies a method that provides an extension. In this case, our method takes three “blocks” and combines them together into a single one.
- Simply having this class in project - or in a referenced assembly - would be enough to make it available for use, but because it’s opt-in the only methods that are affected would be those that want it.
Of course, the classic - and perhaps the simplest - application would be for Notifying properties:
This would allow a very simple declaration: