Alex Mykyta

I'm having the same issue, however I already explicitly denote the `--cov=` option. Similar to @lhupfeldt, I always test with the installed package since in the case of `systemrdl-compiler`, I...

Tried enabling `COVERAGE_DEBUG=trace` but it did not yeild any interesting messages to explain why coverage was getting skipped: ``` Not tracing '/home/alex/Desktop/SystemRDL/systemrdl-compiler/test/.venv/lib/python3.8/site-packages/pytest_cov/compat.py': module 'pytest_cov.compat' falls outside the --source spec Not...

Sure - to reproduce in my project: * Clone https://github.com/SystemRDL/systemrdl-compiler * `cd systemrdl-compiler/test` * `./run.sh` Tests run twice, with & without the C++ accelerator extension. You can prune some steps...

Commenting here since this thread shows up in Google searches often. There's no need to pin to an older version of coveralls. Instead, make sure you are *not* installing `coverage`...

Created a patch script that implements this optimization: https://gist.github.com/amykyta3/8285559e95074c4431c2836d78b36530

Created a patch script that implements this optimization: https://gist.github.com/amykyta3/8285559e95074c4431c2836d78b36530

The behavior of a user defined property's `default` setting is often misinterpreted and this is actually the intended behavior. See my reply in #30 for a detailed explanation.

@j-klier Re-opening this, since I missed your detailed reply after I initially had closed this. In principle, I totally agree with you on what the `default` keyword *ought* to do....

Aagh! Now I'm not totally convinced. Looking at the full `15.2.2-Example1` again, there is another snippet that is interesting: ```c property some_num_p { type = number; default = 0x10; component...

Currently, all parameters get evaluated into constants and finalized at compile-time. Currently there is no way to "float" a parameter to the output. That said, I have considered adding this...