no you can't do nested accessors like that just now. In 3.2 we will most
likely alllow it by converting it to a predicate (which has a runtime
performance penalty that most people won't notice, but its necessary as
nested structures are kind of unsafe for rete, but nevertheless for the end
user
Looks like 3.2 will have a lot features related to accessing field
values, when approximately it will be released?
Michael Neale wrote:
no you can't do nested accessors like that just now. In 3.2 we will
most likely alllow it by converting it to a predicate (which has a
runtime performance
end of Q1 next year.
Mark
Alexander Varakin wrote:
Looks like 3.2 will have a lot features related to accessing field
values, when approximately it will be released?
Michael Neale wrote:
no you can't do nested accessors like that just now. In 3.2 we will
most likely alllow it by converting
Assuming I have folllowing structure of an object A that I want to use
for building LHS conditions:
Class A {
b: Class B {
attr1: String;
}
...
}
I get error messages if I try get A.B.attr1 in the following way:
When
a: A($param1: b.attr1)
