• I have tried using the latest released version of Numba (most recent is
  visible in the change log (https://github.com/numba/numba/blob/main/CHANGE_LOG).
• I have included a self contained code sample to reproduce the problem.
  i.e. it's possible to run as 'python bug.py'.

I think I have discovered a very minor bug - or rather inconsistency with numpy - in Numba's implementation

Auto-Installer is currently not supported on Windows platforms. TVM and TensorRT in particular would need special care.

Support &, |, ^, etc.

Make a concise print function for the QueryPlanningAnalysis class https://github.com/kensho-technologies/graphql-compiler/blob/v2.0.0.dev25/graphql_compiler/cost_estimation/analysis.py#L381

In most cases, the printout of the analysis passes is enough to explain why a particular query plan was chosen.

FINN has a Vivado version requirements, e.g. 2019.1 in the 0.2b release. The available Vivado version should be checked before any Vivado-related commands are launched, and an assertion should be raised if there is a version mismatch.

We should use a round-robin strategy here to assign these free equations. Otherwise, mesh 0 will run out of memory
https://github.com/alpa-projects/alpa/blob/8d69815db9617a9e720927c39ad5bde01fd06f0f/alpa/pipeline_parallel/apply_grad.py#L623-L625

ARTIQ Feature Request

Problem this request addresses

It would be nice to access scan objects like RangeScan through indexes such as RangeScan[0] (which now is available as RangeScan.start) etc.

Describe the solution you'd like

This seems doable by defining a __getitem__() method for the scan classes?
If the sequence is predefined/allocated in the constructor then there s