Joel Bodenmann

Personally, I'd want to wait with migrating "everyting" to co-routines anyway. I looked into this when starting to write this library and compiler support seemed less-than-ideal. I am still thinking...

> I like the custom error reporting interface in theory, but I'm not clear on what form that would take. Me neither - otherwise this would have been done long...

Well, I couldn't agree more. This is a very good write-up of my thoughts of the last few weeks/months. Thank you for going through the trouble of writing this out...

@0x00002a do you see any scenario that would justify implementing this in a way that a user can inspect whether one or more redirects were followed or should this just...

@0x00002a how busy are you currently? I'd really like to move to the first release ASAP to make maintaining applications consuming this library easier and hopefully also attracting more users...

Yeah, I have been looking at [this](https://github.com/CPPAlliance/url) for a while now. It didn't even have an alpha release when I started writing this library. That's why I added my own...

I think we should aim for not including this in the initial `v0.1` release given the complexity / nature of intrusive changes if we implement it properly.

I'm all pro adding a `.clang-format` file and adding it to the CI/CD pipeline. This is also already on the project's ToDo list. I should probably add that ToDo list...

I will create a corresponding `.clang-format` soon.

I've added a preliminary `.clang-format` to the repository. I might still tweak it tho. Seems like we need something like this: https://github.com/marketplace/actions/clang-format-check