Re:How Microsoft rewrote its C# compiler in C# and made it o...
by Const-me on Thursday February 13, 2020 @04:56AM
(#22316529)
My experience might be irrelevant to Roslyn, I experienced these things when reporting Visual Studio bugs in general. Examples:
https://developercommunity.visualstudio.com/content/problem/... (BTW, people have been reporting that bug for years now)
https://developercommunity.visualstudio.com/content/problem/...
https://developercommunity.visualstudio.com/content/problem/...
https://developercommunity.visualstudio.com/content/problem/...
You can also see that there are many more resolved issues in previews of that public release: https://github.com/dotnet/roslyn/milestones?state=closed
So there are a _lot_ of legitimate problems being fixed and enhancements being added over pretty short periods of time.
When something is resolved as "no reproduction" or "not a bug", that's because there was an earnest attempt to reproduce an issue with the latest bits set to go out to a release with no reproduction, or something is truly by design (e.g., user files an issue because they would prefer a feature to do something different than it does today).