Chris Leary

Also note relates to discussion in #578 -- "easy stitching of XLS components into pre-existing external-world environments" is something we can make more streamlined out of the box, given the...

cc @sandwichmaker

Not currently on the "implement soon" radar so marking as long-term enhancement.

I presume you mean a lightweight analysis that would just say "hey it's clearly unused and so this can't be right", i.e. "must not be dead" (since we can't determine...

Also taking this issue as an opportunity to plumb through the open source backend flow as Bazel rules so we can inspect the P&R'd result for various lowerings, labeling it...

@ted-xie Did it feel like the obstacles could be handled with a rewrite / "early rejection script" pre-pass kind of thing? (I imagine one of the challenges is that most...

The fuzzer internals have changed quite a bit, this might be better reframed as "port the remaining fuzzer infrastructure to C++" -- we'll probably get a speedup over the current...

Just a note that #207 is very related, both all about constexpr evaluation.

I think I failed to realize on my first reading this is actually an *array* slice, not a *bit* slice. So blocked on https://github.com/google/xls/issues/312 and https://github.com/google/xls/issues/126

@meheff I think we've probably reached a stable state on this one, even if we've talked about alternatives -- want to summarize so we can close this out?