Roger Peppe

The [type system description](https://kocircuit.github.io/language/types/index.html) doesn't say whether a variety type can be part of option, sequence or struct types. Likewise, the [unification description](https://kocircuit.github.io/language/types/unification/index.html) does not seem to say how variety...

I've probably missed something, but the unification rules seem incomplete. Are there any unifications rules between different integer sizes, for example? Perhaps something like this might suffice (assuming that's what...

This error is occasionally observed from the api/client package when running tests: ``` --- FAIL: TestRulesetService/WatchRuleset/Cancel (0.00s) require.go:1209: Error Trace: rulesets_test.go:430 Error: Should be zero, but was {0xc000222de0 } Test:...

### What version of CUE are you using (`cue version`)? $ cue version cue version v0.0.0-20220915174651-ad253ed099e9 -compiler gc CGO_ENABLED 1 GOARCH amd64 GOOS linux GOAMD64 v1 vcs git vcs.revision ad253ed099e94ddcffd07e6f73a76735a96cfaf8...

provide better ways to surface errors involving files that aren't on disk

5

When using CUE as part of a program's operation (for example to validate a configuration file read by a Go program), the schema is often embedded inside the program. That...

### What version of CUE are you using (`cue version`)? $ cue version cue version v0.0.0-20220901114913-d2250b9bc187 -compiler gc CGO_ENABLED 1 GOARCH amd64 GOOS linux GOAMD64 v1 vcs git vcs.revision d2250b9bc1870a2488ee3f33b4e8e4fd0561a5f3...

### What version of CUE are you using (`cue version`)? cue version v0.0.0-20220815180243-e187f9fe5d45 -compiler gc CGO_ENABLED 1 GOARCH amd64 GOOS linux GOAMD64 v1 vcs git vcs.revision e187f9fe5d456f14073645670a98803d3048849e vcs.time 2022-08-15T18:02:43Z vcs.modified...

etld/fsm.go triggers pathological compiler case

1

I tried to compile it under Go 1.7rc1 and the compiler never completed. See https://github.com/golang/go/issues/16407 - there's a suggestion by @josharian for a possible way to work around the issue...

type matching should match unqualified names

6

The [specification](https://avro.apache.org/docs/current/spec.html#Schema+Resolution) says: > [to match] both schemas are records with the same (unqualified) name However [the code](https://github.com/actgardner/gogen-avro/blob/master/compiler/method.go#L164) checks the fully qualified names, leading to an "Incompatible types by name"...

It is not entirely clear whether the rate would allow arbitrary floating point numbers (for example in exponent location, 0.4e-5) or whether the decimal form is required. It doesn't mention...