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

Typescript Spec for Typeguard #1626

Closed
yuit opened this issue Jan 9, 2015 · 1 comment · Fixed by #1878
Closed

Typescript Spec for Typeguard #1626

yuit opened this issue Jan 9, 2015 · 1 comment · Fixed by #1878
Assignees
Labels
Bug A bug in TypeScript Fixed A PR has been merged for this issue Spec Issues related to the TypeScript language specification

Comments

@yuit
Copy link
Contributor

yuit commented Jan 9, 2015

Since we have changed type guard behavior in PR #1621, #1433, should we update the language spec to reflect these change?

@danquirk danquirk added Bug A bug in TypeScript Spec Issues related to the TypeScript language specification labels Jan 9, 2015
@danquirk
Copy link
Member

danquirk commented Jan 9, 2015

We should make sure we have spec issues for any other changes since the last update.

@mhegazy mhegazy added this to the TypeScript 1.5 milestone Jan 12, 2015
@ahejlsberg ahejlsberg added the Fixed A PR has been merged for this issue label Feb 2, 2015
@microsoft microsoft locked and limited conversation to collaborators Jun 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug A bug in TypeScript Fixed A PR has been merged for this issue Spec Issues related to the TypeScript language specification
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants