问题
After switching to Visual Studio 2015, we have noticed that some changes made to how lambdas are compiled to MSIL in Roslyn (described in this thread and on GitHub) introduce runtime failures under certain conditions.
Since Roslyn is obviously the future of .NET, we would like to switch to this technology, but it seems that all legacy code which has been running in production (and where we have a fair degree of confidence it works correctly) is now prone to new runtime failures. These are several libraries which are impacted by this issue also (like Moq, for example).
We already skipped the upgrade to RyuJIT for its issues, but I believe Visual Studio 2015 is heavily integrated with Roslyn and I don't think we can simply replace the csc.exe manually (but that's a different question).
So, is there a compiled list of breaking changes in Roslyn which we could reference to see what we can expect?
回答1:
(Update)
Thanks to @NealGafter for providing the link. The list of breaking changes can currently be found here:
- Roslyn Github issue 7278: List of breaking changes in Roslyn
It seems that some documentation is supposed to be here: Roslyn Compiler Specification (roslyn/docs/compilers on GitHub). According to the description:
The compiler specification details the supported (and semi-supported) surface area of the Roslyn VB and C# compilers. This includes
- Command-line switches and their meaning
- Breaking changes from previous versions of the compilers
- Compiler behaviors that are (intentionally) contrary to the specification
- Compiler features not described by the language specification
- COM-specific and other Microsoft-specific features
- "Well-known" attributes that affect compiler behavior
- The "ruleset" file syntax and semantics
- Features included for interoperability between C# and VB, for example
- Named Indexers use from C#
- Places where the compiler behavior diverges from the language specification
- Limitations (e.g. identifier length)
- History of language changes per version
The document describing changes to CodeGen regarding lambdas (because this was my initial issue) is at roslyn/docs/compilers/CSharp/CodeGen Differences:
Non-lifting Lambda expressions are now implemented as instance methods on singleton display classes. Since the entry point to the delegate is the instance "Invoke" method, it is cheaper at runtime to dispatch delegate invocations to the underlying implementing method if such method is also an instance method with exactly same formal signature as "Invoke".
来源：https://stackoverflow.com/questions/33954768/list-of-breaking-changes-in-roslyn