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

the cast<>() operator throws parse-time exceptions with hashdecls that may succeed at runtime #4531

Closed
davidnich opened this issue May 16, 2022 · 0 comments

Comments

@davidnich
Copy link
Contributor

when a user uses cast<>(), we need to trust the user that it will work at runtime if it can possiblty work, parse-time errors should only be thrown if Qore is sure that the runtime will always fail.

@davidnich davidnich added this to the 1.7.3 milestone May 16, 2022
@davidnich davidnich self-assigned this May 16, 2022
@davidnich davidnich added this to To do in Qore Development via automation May 16, 2022
davidnich added a commit that referenced this issue May 16, 2022
refs #4529 fixed type handling with complex hash - string|ist
refs #4531 fixed a bug in the cast<>() operator with hashdecls where a parse-time exception could be thrown for an operation that could succeed at runtime
davidnich added a commit that referenced this issue May 16, 2022
…ion (#4530)

refs #4529 fixed type handling with complex hash - string|ist
refs #4531 fixed a bug in the cast<>() operator with hashdecls where a parse-time exception could be thrown for an operation that could succeed at runtime
Qore Development automation moved this from To do to Done May 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

1 participant