mikex-oss

> We should split pip.bzl up to better separate the repo-rules from regular-rules. Is this something the Bazel team will consider? > Or maybe put a call to py_repositories in...

> Is this still relevant? If there has been any suspected fix for this issue, happy to give it a try. We are still using rules_python-0.25.0 to avoid this problem.

FYI, the bazel rule is already being changed for #1415 > Change default comparison method to none to avoid confusing errors when multiple procs are defined in a test.

In the spirit of https://github.com/google/xls/issues/415, this would also provide familiarity to hardware engineers, who can use the `{ }` assignment pattern in SystemVerilog, e.g. `assign {baz, bar, foo} = some_bigger_vector;`

I was reminded today of this because I ran into the `Standard style is SCREAMING_SNAKE_CASE for constant identifiers` error. It seemed surprising that DSLX enforces some style as errors when...

@cdleary you 100% know more about Rust than me, so thanks for pointing out that Rust also has some built-in warnings that enforce standard code style. But if I'm not...

Related: #1387 However, there, note that the repro produces a reasonable error for bit slices: ``` TypeInferenceError: Unable to resolve slice start to a compile-time constant. ``` It's array indexing...

Discussed this over another lunch conversation with @grebe and @hongted a short while back. It seems like if you treat early returns as an implicit "else" around the rest of...

> Is this example equivalent to the one w/ early returns? @proppy you're right! (I'll leave that error there rather than editing it though.) While not intentional, it does sorta...

+1. Just ran into this myself. In my case, the `zero!` is within a parametric function intended specifically to adjust the array size of the struct. So it's not really...