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

Numbers #58

Open
gioannides opened this issue Jan 20, 2018 · 3 comments
Open

Numbers #58

gioannides opened this issue Jan 20, 2018 · 3 comments

Comments

@gioannides
Copy link

  1. is a valid input, this will be interpreted as 1
    .1 is not valid (it is not 0.1). Should it be considered as 1 or be considered invalid altogether?

Same applies for 1/0, should this be interpreted as two independent number 1 and 0, or should it be disregarded altogether as invalid?

@mahudu97
Copy link

.1 should be interpreted as 1: should ignore the '.' and start from '1' to find a matching pattern.
The spec has no case for a token starting with '.' - so it should be ignored.

For 1/0, DT has mentioned that although it should be treated as 1 and 0 as two separate integers, he will not be testing this case as it wasn't specified at the start - so don't worry about 1/0.

@m8pple
Copy link
Contributor

m8pple commented Jan 24, 2018

Yup, exactly what @mahudu97 said.

@gioannides
Copy link
Author

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants