Replies: 1 comment 3 replies
-
You'd first have to fork the repo. We would not accept the changes you're describing into Roslyn itself (as this would no longer be c#), but you're free to fork and take the language wherever you want to. Once forked, I'd recommend looking into LanguageParser.cs and see how we parse actual linq queries. You can then start extending that however you want. Once you extend the syntax, you'll then figure out how to 'bind' it (give it semantic naming y), and finally how to 'emit' it (produce the IL that actually executes in the clr at runtime). |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I am quite new to "roslyn" compiler architecture and what I currently understand, is, that it is a very powerful tool. And that it is possible to somehow extend any implemented language with "custom" contextual keyword.
Does anybody have an idea where to start, to implement simple "SQL integrated query" support for regular SQLs (select, types of join, aggregates, etc. ), that would be written almost similar that are inside SQL with defined single class per table.
for example(select at "end" is by intent - similar way as linq):
Beta Was this translation helpful? Give feedback.
All reactions