Chris Leary
Chris Leary
@jbaileyhandle Very interesting, the fuzzer OOM could be also why our nightly worker blows up. I'll file an issue and look into that. Maybe something different about google3 multiprocessing vs...
We instantiate parametrics in a demand driven fashion (instead of proving a parametric holds "for all x", we instantiate for concrete values of x at a given invocation site). For...
cc @hmontero1205 In #70 support for quickchecking non-parametric functions is introduced -- we'll want a way to let the quickcheck "driver" instantiate parametric functions with the ability to put constraints...
As noted in #526 follow on to #617 will be implementation of monomorphized traits.
As reflected in #526 an outstanding request has been to support methods on struct instances so folks can use the familiar "object oriented receiver" style function invocations -- without polymorphism...
As mentioned in #526 there is an outstanding discrepancy between DSL multidimensional arrays and Rustic ones. I do think the DSL ones we formulated this way before we got serious...
These may only be present in unopt builds, but we still want to be able to JIT compile unopt IR. Simplest example I believe is: ``` concat.1: bits[0] = concat()...
Really we should add generation of match constructs to the fuzzer. Found a bug in single-arm matches (just a single wildcard arm) where the JIT miscompares with the DSL.
Right now we require users to build XLS from source, which can take a long time because of some of our larger dependencies [1](#footnote1) (e.g. LLVM, Z3) and requires users...
We should either auto-proc-ify the function so that the flag can apply or give an error that the flag does not apply to function top levels.