Alex Solovey

This library is considered rather low-level, and so original intent was to provide building blocks for advanced uses, instead of trying to implement all of them in the library itself....

Passing Unicode data down to network or protocol internals causes even more obscure errors, and this is why there is an argument validation step to prevent accidental use of utf8...

This is what happens with your example on bf76926: ```bash $perl -E 'use Kafka::Connection;my $h = 'localhost';utf8::upgrade($h);Kafka::Connection->new(host => $h);' Unicode data is not allowed: host Trace begun at lib/Kafka/Connection.pm line...

While it my seem inconvenient sometimes, the current behavior was (AFAIK) designed to be consistent and predictable. If there may be Unicode data in input, it should be taken care...