Skip to content

Take runtime semantics of numerically named properties into account. #860

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

Merged
merged 9 commits into from
Oct 17, 2014

Conversation

DanielRosenwasser
Copy link
Member

No description provided.

@mhegazy
Copy link
Contributor

mhegazy commented Oct 9, 2014

should also handle #728

To be fair, I don't think humanity knew about negative numbers until like 200 B.C.E.
Conflicts:
	tests/baselines/reference/numericIndexerConstrainsPropertyDeclarations.errors.txt
Specifically, a numeric property is simply now any property whose name N is equal to ToString(ToNumber(N)).
@DanielRosenwasser DanielRosenwasser changed the title Use our own scanner for 'isNumericName'. Take runtime semantics of numerically named properties into account. Oct 10, 2014
Conflicts:
	src/compiler/checker.ts
	tests/baselines/reference/numericIndexerConstrainsPropertyDeclarations.errors.txt
	tests/baselines/reference/numericIndexerConstrainsPropertyDeclarations2.errors.txt
DanielRosenwasser added a commit that referenced this pull request Oct 17, 2014
Take runtime semantics of numerically named properties into account.
@DanielRosenwasser DanielRosenwasser merged commit ad6203f into master Oct 17, 2014
@DanielRosenwasser DanielRosenwasser deleted the numbersAreHard branch October 17, 2014 02:31
@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
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants