Roslyn
Fewer than 5 people recommend it so far, so there's no written verdict. Here is what commenters said.
Why people recommend it
“make compilation much stricter with Roslyn analyzers”
“With Roslyn APIs, strong typing, structured namespaces, and compiler level semantic information”
Show 1 more
“At work we've added multiple Roslyn analysers to our build pipeline”
Caveats and dissent
“Roslyn API, setting up the project”
“Working with the raw Roslyn types is painful at best”
Often compared with
From the makers not counted in the ranking
“In Roslyn the design is a highly concurrent, multi-threaded feature-set that wants to share immutable data.”
“The approach of all of this has several benefits.”
“Roslyn was designed from day one for IDE scenarios.”
Threads where it came up
- Tree-sitter vs. Language Servers 3 mentions
- Comptime – C# meta-programming with compile-time code generation and evaluation 2 mentions
- C# now beats Rust on WASM size 1 mention
- GPT 6.1 Sol: Near-Astra intelligence for a fifth of the price 1 mention
- Herbie: Automatically improve imprecise floating point formulas 1 mention
- Banned C++ Features in Chromium 1 mention
Data: roslyn.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 8
“make compilation much stricter with Roslyn analyzers”
“With Roslyn APIs, strong typing, structured namespaces, and compiler level semantic information”
“instruments Roslyn to find FP and FP-in-loop hotspots across the codebase.”
“you would normally implement rules like this with a custom Roslyn Analyzer”
“At work we've added multiple Roslyn analysers to our build pipeline”
“Roslyn API, setting up the project”
“Working with the raw Roslyn types is painful at best”
“combining Roslyn analyzers with an LLM and a human in the loop could be game changing”