This repository was archived by the owner on Jul 15, 2023. It is now read-only.
Fix for Roslyn async methods#74
Merged
SergeyTeplyakov merged 2 commits intomicrosoft:masterfrom Jun 26, 2015
Merged
Conversation
…rts back initial state machine value that was used for getting method contract in async methods generated by Roslyn compiler. Add VS14RC compiler to the tools, added test that checks the fix by using Roslyn-based compiler. Add missing native dependencies for v4.5 compiler.
Contributor
|
Looks great! Please merge this in. |
SergeyTeplyakov
added a commit
that referenced
this pull request
Jun 26, 2015
Fix for Roslyn async methods
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This fix should resolve #51.
I've added latest Roslyn-based csc compiler to the tools folder and modified the tests to use it.
Unfortunately my change revealed some issues (#69, #70, #72), that should be fixed (IMO) before releasing new CC version.