gojimmypi

this is a known issue. workaround is to place a space after the `*` as the current logic does not properly distinguish comment chars: `//` and `/*` and `*/` ```...

I'm pretty sure your fix did not break that. yes, there are a variety of "strange things" that happen. I had a chance over the weekend (such as #16) to...

ya, I hear you on the "_too much work_". after a week of programming at the day job, here I am doing some relaxing coding on the weekend. ;) I'm...

@Risavk heads up I've pushed all my latest code to [development-interim](https://github.com/gojimmypi/VerilogLanguageExtension/tree/development-interim) branch: Some performance improvements, but nearly as much as I'd like. Still too much time spent re-parsing needlessly. Handling...

Hi @kumekay the 3rd party preview signup link is currently 404. I'd like to add the wolfSSL component to the Espressif component registry. Per a discussion with @igrr and noted...

Hi @kumekay that's awesome, thank you! email sent.

Following up on this issue: the ESP Registry is really quite nice, the [latest docs](https://docs.espressif.com/projects/idf-component-manager/en/latest/guides/packaging_components.html) are very clear. I have wolfSSL published at https://components.espressif.com/components/wolfssl/wolfssl Thank you @kumekay for your help....

@dgarske - question on the benchmarks fix data size vs fixed time: In the `master` and `riscv_aes_asm` branch you [ran](https://github.com/wolfSSL/wolfssl/pull/7569#issuecomment-2132248155) these commands, respectively: ``` # before, on master ./configure —enable-all...

jenkins retest this please

jenkins retest this please