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
Type checking a mapping/listing should be lazy #406
Labels
bug
Something isn't working
Comments
This is just another example. The addition happens and we get 33 but at what point is the type checking meant to happen. Using the IntelliJ plugin I get warnings telling me I'm doing something stupid. foo = new Listing<YamlRenderer> {
11
}
bar = new Listing<String> {
22
}
output {
value = foo[0] + bar[0]
renderer = new YamlRenderer{}
} output 33 |
@harryjackson: what you're seeing is the #405 bug, rather than this one. To fix, you should add a type annotation to your properties: foo: Listing<YamlRenderer> = new {
11
}
bar: Listing<String> = new {
22
}
output {
value = foo[0] + bar[0]
renderer = new YamlRenderer{}
} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, accessing a property of type
Mapping<TypeA, TypeB>
orListing<Type>
will shallow-force the whole mapping/listing. The shallow-force gets skipped if the type isunknown
orAny
(e.g.Listing
, orListing<unknown>
, orListing<Any>
).This should not throw, but does currently:
This is related to #405
The text was updated successfully, but these errors were encountered: