Tim Hutt

> Hmm interesting. Can you check if it also works for option names? I mean like --cool_option gets transformed into cool-option? Thanks :) Yep that's how I'm using it. ```...

Agreed. Also it would be nice if it supported sending the form data as multipart/form-data instead of JSON.

I have rebased, formatted and squashed it. Unfortunately there are two issues I found: 1. The `escaped_doc_comment_description` test fails due to an extra newline. 2. You can't start a description...

The spec is very unclear on this. It says > Regardless of success or failure, executing an SC.W instruction invalidates any reservation held by this hart. which really *sounds* like...

Sounds logical - I just think the difference between executing but failing an SC and executing but trapping needs to be explicit. It's quite vague at the moment. Something like:...

I have this issue too. I think it *is* a network failure, even if you already initialised pre-commit. I think the issue is that the pre-commit install hook doesn't *actually*...

Yes, but unfortunately that doesn't help because if you run `pyright` via `pre-commit` it isn't actually installed for the user, so when I run `pyright --help` it just says `pyright:...

I also experience this error. Here's my code: ``` #include #include #include #include #include #include #include int main(int argc, const char* argv[]) { SoundIo *soundio = soundio_create(); int err =...

Actually cancel this. It's literally impossible to have a short enough path on Windows so you cannot use this project on Windows at all.

Shouldn't the Troubleshooting section be for issues that *might* occur? This issue is going to be hit by *every* Windows user (unless they're extremely lucky) so it makes sense to...