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

inconsistent type handling with complex types #3278

Closed
davidnich opened this issue Jan 23, 2019 · 0 comments
Closed

inconsistent type handling with complex types #3278

davidnich opened this issue Jan 23, 2019 · 0 comments

Comments

@davidnich
Copy link
Contributor

ex:

david@greybeard:~/src/qore/git/qore/src$ qore -nX 'hash h = map {$1: True}, (auto x = ())'
<EMPTY HASH>
david@greybeard:~/src/qore/git/qore/src$ qore -nX 'hash<string, bool> h = map {$1: True}, (auto x = ())'
unhandled QORE System exception thrown in TID 1 at 2019-01-23 10:41:28.056761 Wed +01:00 (CET) at <command-line>:1 (Qore builtin code)
PARSE-TYPE-ERROR: lvalue for assignment operator '=' expects hash<string, bool>, but right-hand side is hash<string, bool> or no value (NOTHING)
@davidnich davidnich added this to the 0.9 milestone Jan 23, 2019
pvanek added a commit that referenced this issue Jan 25, 2019
refs #3278 fixed complex type handling to be consistent with non-comp…
davidnich added a commit that referenced this issue Aug 18, 2019
davidnich added a commit that referenced this issue Aug 19, 2019
davidnich added a commit that referenced this issue Aug 19, 2019
* refs #3278 more type and doc fixes

* refs #3278 minor doc update
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant