3a67f91228
Using `OpAttrSelect`, the ? operator will fail when encountering a
nested value that is not an attribute set.
This however breaks valid code, such as:
{ bs = 42; } ? bs.a.b
The fix is simply to use the same operator used in the `or` statement,
which leaves a sentinal on the stack if a field is not found or the
value is not an attribute set.
Change-Id: Ib28fc8a96e6d592b4cdbc3e65ba129ad8faecd66
Reviewed-on: https://cl.tvl.fyi/c/depot/+/6211
Reviewed-by: grfn <grfn@gws.fyi>
Tested-by: BuildkiteCI
|
||
|---|---|---|
| .. | ||
| tests | ||
| value | ||
| chunk.rs | ||
| compiler.rs | ||
| disassembler.rs | ||
| errors.rs | ||
| eval.rs | ||
| lib.rs | ||
| main.rs | ||
| opcode.rs | ||
| vm.rs | ||
| warnings.rs | ||