Unions coming in .NET 11 / C# 15 are going to be great.
C#/.NET feels unreasonably effective as a target for LLMs. The reflection and compiler services are not found anywhere else and have profound effects that HN still seems to be taking massive naps on.
"Read the relevant design documents under docs/ before changing architecture."
makes me think that developing 'graphify the tool' and using 'graphify as a tool' are mixed up in the same document? How does an LLM keep track of both this gigantic skill and the user development problem at the same time?GitHub Copilot's semantic index can work for any SaaS repo provider (GitLab, Bitbucket, etc.) or any local repos but this requires you to opt into the feature. Repos hosted in GitHub and Azure DevOps do NOT require opting into it since Microsoft already has your code.
EDIT: I think the differentiation is that this isn't MCP based. Dumping a portable json file allows much more flexibility than just having to run Rider IDE in the background with the solution loaded and indexed. e.g. the graph works with jq, CI (gates), arbitrary agents without MCP support, non MCP tools, bulk questions etc.