3 ms·
Sadly expression trees got out of love in modern .NET and it remains to be seen how much they will ever improve them. https://github.com/dotnet/csharplang/disc
by pjmlp 2y ago
Sadly expression trees got out of love in modern .NET and it remains to be seen how much they will ever improve them.
https://github.com/dotnet/csharplang/discussions/158 https://github.com/dotnet/csharplang/discussions/158
- shellac 2y agoJava has two somewhat related projects in this space, and it does add a substantial cost to language changes (assuming you commit to keep expression trees up to date). https://openjdk.org/projects/babylon/ https://openjdk.org/projects/babylon/ is the most interesting to me, as a linq+++ potentially.
- pjmlp 2y agoYes, being on both ecosystems most of the time, means I get to have lots of nice toys both ways, with them counter influencing each other all these years.
- contextfree 2y agoThe last comment thread by agocke is interesting. I've thought before that it's unfortunate that LINQ and expression trees were implemented before the move to Roslyn, because if they'd been implemented afterwards they could maybe have just directly used the same object model that the compiler itself uses, which could make it more sustainable to keep them in sync with language changes.