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

Correctly handle toInt() as non-constant #8777

Closed
iposva-google opened this issue Feb 25, 2013 · 1 comment
Closed

Correctly handle toInt() as non-constant #8777

iposva-google opened this issue Feb 25, 2013 · 1 comment
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. closed-obsolete Closed as the reported issue is no longer relevant type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@iposva-google
Copy link
Contributor

Once issue #8756 is resolved by Gilad we can correctly implement the expected behaviour in the VM.

@iposva-google
Copy link
Contributor Author

Removed Priority-Medium label.
Added Priority-Unassigned label.

@iposva-google iposva-google added Type-Defect area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. labels Jun 5, 2013
@kevmoo kevmoo added type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) and removed priority-unassigned labels Feb 29, 2016
@zanderso zanderso added the closed-obsolete Closed as the reported issue is no longer relevant label Jan 5, 2017
@zanderso zanderso closed this as completed Jan 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. closed-obsolete Closed as the reported issue is no longer relevant type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Development

No branches or pull requests

3 participants