I see comments suggesting adding this to understand how loops are being handled by numba, and in the their own FAQ (https://numba.pydata.org/numba-doc/latest/user/faq.html)

from llvmlite import binding as llvm
llvm.set_option('','--debug-only=loop-vectorize')

You would then create your njit function and run it, and I believe the idea is that it prints debug information about whether

The GitHub label "good-first_bug" is empty. It is linked to from https://github.com/hylang/hy/blob/master/CONTRIBUTING.rst and the read the docs version.

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.

Bug Report

We are using a very simple way to log. We have this logging context class, and it just prints everything if logging is enabled and that's it. What about enhancing this?

Any opinions are welcome.

For example, a tag is given to each log line and we can only log things with the specified tag or everything ot