Marcel van Lohuizen
Marcel van Lohuizen
@rogpeppe @felixge: I'm a bit ambivalent about what the default should be, but at the very least it should be consistent with the behavior for other formats. Since the default...
Simplification 1: ``` import "math/bits" z: [0, bits.Set(*z[0] | 0, 0, 0)][1] // Same error ``` Simplification 2: ``` z: [0, z[0]][1] // results in `_` ```
BTW, it is correct for this to be an error. The error message is just confusing. The old evaluator was incorrect here: `z` is an integer value in the final...
That is an interesting question. One could argue that this is a clear bug and not intended. So I would say it is preferable fail here. That said, this works...
Fix for V3 identified. Won't fix V2
Theoretically this is not an error. It basically is an elaborate way of specifying that `x` must be the empty list. I agree that `vet` could be stricter and give...
`&` does not "pick" a default (see spec). So `foo.b & bool` results in `false`.
Defaults are not picked by taking a reference. Moreover, terms within a marked default that themselves are disjunctions have their defaults erased. The spec is quite explicit about this, although...
@rogpeppe > In general if I see a reference, ISTM that it should always refer to the final value of the thing referred to. Anything else seems like it's going...
@verdverm This is a very interesting case. Definitions are indeed recursively opened according to the spec, although there are cases where it does not erroneously. But arguably it should not...