Luke Bakken

> It's dangerous! A change about this must have months of communication previously. To explain the change. @luizcarlosfaria this change will go into version 7, which is a major update...

@domicioam please understand that when we suggest opening a pull request to fix issues it is to confirm that yes, the issue is valid and that yes, we would appreciate...

> I am not sure if that was the intention. I felt like the other guy was calling me lazy for reporting it instead of fixing it. I am certain...

> Is there an issue logged for this request? Not at the moment, and I wouldn't worry about an issue for it. If the work could be a follow-on to...

Moving this to version `7.0.0` because - * A workaround exists - https://github.com/rabbitmq/rabbitmq-dotnet-client/issues/650#issuecomment-526916650 * A real fix is a large change to this library ("async versions of all RPC interactions")...

@michaelklishin the 7.x branch has been abandoned - https://github.com/rabbitmq/rabbitmq-dotnet-client/issues/1159#issuecomment-1062046921

There is some relevant discussion here: https://github.com/rabbitmq/rabbitmq-dotnet-client/pull/1110

No worries @danielmarbach I've been too busy with other RMQ related work to do much with this library recently.

I'll be out next week. I haven't forgotten, but it's PTO season these days :smile:

Feel free to submit a pull request implementing your suggestion.