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.

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

Document "Better Betterness" for C# 6 and the compat fix #7934

Merged
merged 1 commit into from
Feb 11, 2016

Conversation

gafter
Copy link
Member

@gafter gafter commented Jan 13, 2016

described in #6560 and #7727.

You can find the docs pretty-printed at https://github.com/gafter/roslyn/blob/doc6560/docs/specs/CSharp%206/Better%20Betterness.md
@AlekseyTs @MadsTorgersen Please review
/cc @dotnet/roslyn-compiler FYI

@gafter gafter added this to the 1.2 milestone Jan 13, 2016
@gafter gafter added the 4 - In Review A fix for the issue is submitted for review. label Jan 13, 2016
@gafter gafter self-assigned this Jan 13, 2016
@davkean davkean closed this Jan 13, 2016
@davkean davkean reopened this Jan 13, 2016
@davkean
Copy link
Member

davkean commented Jan 13, 2016

(Closing/opening to sync update the merge branch to pick up the build break we just fixed)

@davkean
Copy link
Member

davkean commented Jan 14, 2016

unit test failure due to #6358, can be ignored. I've submit #7940 to fix it.

@TyOverby
Copy link
Contributor

@davkean: Considering that this PR just adds a markdown file, I don't think we need to worry about tests for this one 😝

@davkean
Copy link
Member

davkean commented Jan 14, 2016

@TyOverby Yes, but our aim should be to have green builds regardless. We want devs to have confidence in Jenkins.

@AlekseyTs
Copy link
Contributor

Description of compatibility fix LGTM.

gafter added a commit that referenced this pull request Feb 11, 2016
Document "Better Betterness" for C# 6 and the compat fix
@gafter gafter merged commit c6c606d into dotnet:master Feb 11, 2016
@gafter gafter deleted the doc6560 branch May 24, 2018 19:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants