Pierre Prinetti

I completely agree that (RequestOpts).ContextError must go, since error unwrapping should provide the same capability in a more idiomatic way. I am finding myself in deeper a rabbit hole than...

@gophercloud/core what do you think?

@majewsky Can you please rebase? I think we can then merge :rocket:

hmm what happened to the CI

@majewsky something wrong happened on the Github side. When checking out this branch locally, I get the old commits and not the ones you just force-pushed. Do you mind `git...

Hi @majewsky, thank you for coming forward. We have chosen to take a backwards-compatible approach to most changes, including the adoption of `context.Context`. Now that the main library is ready,...

@majewsky do you have a proposal for errors?

>I could see if I could do this is a tool-assisted mass change That would be ideal; writing a good tool is also contemplated within the "time-consuming effort" I mentioned...

@majewsky what do you think about this for the errors? https://github.com/gophercloud/gophercloud/pull/2906 It's just a draft, but the idea is that you can both `errors.As` with `errors.ErrNotFound` or `errors.Is` with `ErrHTTPCode`...

What I understand from your inquiry is that Gophercloud should provide a more ergonomic way to handle both tracing and cancellation, and that both these requirements beautifully match with the...