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

Jump to bottom

Clarify "is equivalent to" #30488

Closed
bwilkerson opened this issue Aug 18, 2017 · 3 comments
Closed

Clarify "is equivalent to" #30488

bwilkerson opened this issue Aug 18, 2017 · 3 comments
Assignees
@lrhn
Labels
area-specification type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@bwilkerson
Copy link
Member

The specification should be updated to make it clear whether statements of the form "is equivalent to" apply to both static errors and runtime semantics or only the latter. See #30483 (comment) for some context.
@lrhn lrhn added the type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) label Aug 21, 2017
@lrhn lrhn self-assigned this Aug 21, 2017
@lrhn
Copy link
Member

lrhn commented Aug 21, 2017

A specification should be unambiguous.

@eernstg
Copy link
Member

eernstg commented Aug 21, 2017

Addressed in this CL.

@eernstg
Copy link
Member

eernstg commented Aug 22, 2017

Closed in this commit.

@eernstg eernstg closed this as completed Aug 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lrhn lrhn

Labels
area-specification type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lrhn @bwilkerson @eernstg