We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Redigo handles complex types by "converting" them using Fprint which seems like a very odd thing to do.
Fprint
default: var buf bytes.Buffer fmt.Fprint(&buf, arg)
Why use Fprint when there is encoding/gob? I don't really understand the design decision here.
encoding/gob
gob.NewEncoder(&buf).Encode(&arg)
would be more robust.
The text was updated successfully, but these errors were encountered:
See issue #30.
Sorry, something went wrong.
Sorry for the dupe, don't know why I didn't see this.
No branches or pull requests
Redigo handles complex types by "converting" them using
Fprint
which seems like a very odd thing to do.Why use
Fprint
when there isencoding/gob
? I don't really understand the design decision here.would be more robust.
The text was updated successfully, but these errors were encountered: