Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

List of breaking changes in Roslyn #7278

Closed
gafter opened this issue Dec 7, 2015 · 3 comments
Closed

List of breaking changes in Roslyn #7278

gafter opened this issue Dec 7, 2015 · 3 comments
Assignees
@gafter
Labels
2 - Ready Area-Compilers Documentation
Projects
Compiler: Engineering Investments
Milestone
Backlog

Comments

@gafter
Copy link
Member

gafter commented Dec 7, 2015 •
edited

The VS2015 documentation does not include any section on breaking changes in the languages or compilers, even though there are many changes as the compilers were rewritten from scratch.

From stackoverflow:

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?

There are now breaking changes documents in the Roslyn repository under docs/compilers

Many more items need to be copied from our internal "compiler specification".
@atifaziz atifaziz mentioned this issue Apr 30, 2016
Closed
@gafter gafter added this to the 2.0 (RTM) milestone Aug 10, 2016
@gafter gafter self-assigned this Oct 20, 2016
@jcouv
Copy link
Member

jcouv commented Dec 16, 2016 •
edited

We started recording breaking changes introduced by VS 2015 in this document.

@gafter
Copy link
Member Author

gafter commented Dec 16, 2016

@jcouv Not to mention #7278

@jaredpar jaredpar modified the milestones: 2.0 (RTM), 2.1 Jan 12, 2017
@jcouv
Copy link
Member

jcouv commented Jan 21, 2017 •
edited by gafter

We started recording breaking changes introduced by VS 2017 in this document.

@bbarry bbarry mentioned this issue Jan 21, 2017
Closed
@TessenR TessenR mentioned this issue Feb 6, 2017
Open
@controlflow controlflow mentioned this issue Feb 8, 2017
Closed
@jaredpar jaredpar modified the milestones: 3.0, 2.1 Feb 15, 2017
@gafter gafter added this to Documentation in Compiler: Gafter Mar 10, 2017
@gafter gafter modified the milestones: 16.0, 16.1 Feb 26, 2019
@jcouv jcouv modified the milestones: 16.1, 16.2 Apr 23, 2019
@gafter gafter modified the milestones: 16.2, Backlog Jun 3, 2019
@gafter gafter closed this as completed May 14, 2020
@jcouv jcouv moved this from Triage to Closed in Compiler: Engineering Investments Sep 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gafter gafter

Labels
2 - Ready Area-Compilers Documentation
Projects
Compiler: Engineering Investments
  
Closed
Milestone
Backlog
Development

No branches or pull requests
3 participants
@jaredpar @gafter @jcouv