Eric Astor

@proppy - not quite. Think in terms of storage - we don't actually have storage for an unbounded number of future values of state at the same time. We only...

RE: @meheff @hongted - since the interpreter currently uses infinite-depth FIFOs anyway, I'm pretty sure it's a legal evaluation to just interpret all sends as succeeding, so nonblocking sends will...

Looks more likely to be an LLVM or JIT problem? Seems like a case where the optimizations are hiding a difference between the interpreter and the JIT, since unopt JIT...

I think an alternative approach would just be to make tokens valid subjects for array operations. As currently implemented, if XLS were to allow this, the result will be semantically...

When filing multiple bugs, please file them as separate issues. Also, please include details of the observed error in the issue, rather than just attaching reproduction scripts.

The commands you were executing would be important, including a file that lets us reproduce the issue - as would the context. Generally speaking, we expect users to run our...

If that's the commit you're using, you're very nearly two years of frequent commits out of date - I'm not particularly inclined to go hunting to figure out whether `umod`...

Can you share the next line of the error? It might help if we knew which node was unhandled for conversion, since our local tests seem to confirm that `umod`...

@meheff Please rebase this when you can; we can't pull it in for final review until conflicts are resolved.