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

fix: apply automatic type conversion to constant expressions #484

Merged
merged 1 commit into from
Jan 9, 2020

Conversation

mvertes
Copy link
Member

@mvertes mvertes commented Jan 9, 2020

Detect the presence of constant expression for unary operators and
perform computation of result during compile stage instead of exec
stage. It was already done correctly for binary operators.

Apply automatic type conversion not only to literal values but
also to arbitrary expressions where all members derive from a
predefined constant at compile stage.

Fixes #470

Detect the presence of constant expression for unary operators and
perform computation of result during compile stage instead of exec
stage. It was already done correctly for binary operators.

Apply automatic type conversion not only to literal values but
also to arbitrary expressions where all members derive from a
predefined constant at compile stage.

Fixes #470
@mvertes mvertes added area/core bug Something isn't working labels Jan 9, 2020
@mvertes mvertes added this to the v0.7.x milestone Jan 9, 2020
@mvertes mvertes requested a review from ldez January 9, 2020 13:42
@ldez ldez merged commit f1cde2b into master Jan 9, 2020
@ldez ldez deleted the fix-470-constant-expr branch January 9, 2020 17:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/core bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Negative floating point numbers are interpreted as int
2 participants