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

<1i> should be a Complex literal, not ComplexStr #1827

Open
zoffixznet opened this issue May 14, 2018 · 0 comments
Open

<1i> should be a Complex literal, not ComplexStr #1827

zoffixznet opened this issue May 14, 2018 · 0 comments
Labels
data types Arrays, lists, hashes, pair objects, etc.

Comments

@zoffixznet
Copy link
Contributor

When there are no spaces, we use the rule: if it contains an operator, create a numeric literal, otherwise, create an allomorph. So <1/2> has an operator, so it's a Rat, while <1.2> doesn't have an operator, so it's a RatStr. The <1i> does have a postfix operator, so it should come out as Complex, not a ComplexStr.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
data types Arrays, lists, hashes, pair objects, etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lucasbuchala @zoffixznet