The current (as of 72ca60d) pattern for TTransport factories in Golang is
This causes issues, because some TTransportFactory implementations can return and error. Consider the THttpClientTransportFactory, which as of of 72ca60d, includes the following snippet:
The call to NewTHttpClientWithOptions(...) call can throw errors. The resultant behavior is that nil is returned in place of a valid TTransport, with a nil error.
The TTransportFactory interface (and associated use patterns) should be extended to include errors.