We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi! I was expecting the semantics of tuple composition to merge and accrue (for lists) the contents. For example:
a = { config = { exponent = { constant = 0.30 } } }; b = { config = { base = { constant = 2.0 } } }; default = a b
but the result is
+- default | +- config | | +- base | | | +- constant => 2.0
I was expecting both sets of attributes in default. Same behavior with compose_all().
default
compose_all()
Is tuple merging possible in this implementation of gcl, or is only applied in literal syntax? Thank you,
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi!
I was expecting the semantics of tuple composition to merge and accrue (for lists) the contents.
For example:
but the result is
I was expecting both sets of attributes in
default
.Same behavior with
compose_all()
.Is tuple merging possible in this implementation of gcl, or is only applied in literal syntax?
Thank you,
The text was updated successfully, but these errors were encountered: