Skip to content

Conversation

@sandersn
Copy link
Member

Fixes#4669.

The change is extremely small because almost all the machinery is already in place. I decided to give an error for an accessor with one abstract and one not-abstract member. I couldn't come up with a good example with mixed abstractness.

Almost all the infrastructure is in place, so I just allowed abstract properties+accessors and added an error when abstract accessors do not have the same abstractness specified.
1. Positive tests. 2. Negative tests. 3. Update error messages. 4. Remove errors from conformance test.
@RyanCavanaugh
Copy link
Member

👍

"category": "Error",
"code": 2675
},
"Accessors must both be abstract or not abstract.":{

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

non-abstract

Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure

sandersn added a commit that referenced this pull request Feb 22, 2016
@sandersnsandersn merged commit a769ba7 into masterFeb 22, 2016
@sandersnsandersn deleted the abstract-properties branch February 22, 2016 22:17
@microsoftmicrosoft locked and limited conversation to collaborators Jun 19, 2018
Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@sandersn@RyanCavanaugh@DanielRosenwasser@msftclas