-
Notifications
You must be signed in to change notification settings - Fork 420
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.
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
Roslyn 2.6.0 + C# 7.2 #1055
Roslyn 2.6.0 + C# 7.2 #1055
Conversation
filipw
commented
Dec 11, 2017
- upgraded to Roslyn 2.6.0
- added C# 7.2 support
- added a C# 7.2 test for scripting (scripting by design should default to latest language version)
- fixed some tests that contained invalid C#
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! I think you found all of the places. 😄
@DustinCampbell thanks! there is however a weird issue on Travis which seems legit. any idea what could cause this weird exception on Mono?
The only related thing I found is this dotnet/roslyn#22794, could it be a regression on Mono of some sort? |
I think you're right. The exception is coming from here: https://github.com/dotnet/roslyn/blob/de8b37a43d13aeea3a7a8b6bdf33e8363ada4da2/src/Workspaces/Core/Portable/Workspace/Solution/Checksum.cs#L30. I've pinged that PR to see it can be ported to Roslyn master. I don't think this is a regression in Mono. It looks more like some subtle change in Roslyn's solution checksum caused it. I'm starting a mail thread internally to raise the priority. |
Adding a blocked label - pending dotnet/roslyn#23722 |
@filipw : The 2.6.1 Roslyn packages are now available on nuget.org. |
e4f1578
to
5d3207a
Compare
perfect! I updated this PR and now the checks are all passing 🎉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@david-driscoll @DustinCampbell I'm punching this in then 😇 |