Robin Mueller
Robin Mueller
This could be connected to embedded by doing this for a GPIO pin (e.g. Output, Input structures on top of some low-level register access API).
I'll try to fix the CI
Thanks for the excellent explanation, that definitely makes sense. Concerning `Lazy` : I only call the `split_mut` function once at program initialization. So I think this should not be a...
I also strongly support this and would also very much appreciate this in my `no_std` crates :+1:
I once heard/read the door bell rings analogy and I really liked it.
I did a small benchmark between this lib and crcmod (uses C extensions) and fastcrc (wraps Rust library): ```sh spacepackets-py/benchmarks/crc on crc-benchmarking [$!] via 🐍 v3.12.3 (venv) ❯ ./crc_benchmark.py...
> If we could dynamically define the base address of the peripheral, the generated PAC could be shared across different SoCs that share the same peripheral. > It would also...
> @robamu when you say "dynamically" does it mean the address is not known on compile time or just that it can take any value? The value would be known...
Hmm, is this a common solution? is it a large issue that the tests are installed as well? https://packaging.python.org/en/latest/tutorials/packaging-projects/ does not mention any special handling for test files.
Maybe this is also related to the following line: ``` [tool.setuptools.packages] find = {} ``` i need to check whether we still need this.