-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
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
DOC-4996 hiredis docs #1332
DOC-4996 hiredis docs #1332
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice, @andy-stark-redis! Apart from one non-blocking comment, LGTM.
linkTitle: hiredis (C) | ||
title: hiredis guide (C) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not clear to me how hiredis is to be capitalized. The GitHub page uses "Hiredis"; but some blogs use either "HIREDIS" or "hiredis". It's not a showstopper by any means; just me being overly pedantic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, tbh, I just picked one and tried to stick with it :-) I'll be happy to change it if anyone has a definitive version of the name.
Thanks for the review @dwdougherty ! |
Co-authored-by: Igor Malinovskiy <[email protected]>
DOC-4996
Note: there is more to add to the
hiredis
docs, but I thought I'd get some feedback on this basic set. The C code is all tested but I'd be more than happy to hear suggestions for good/idiomatic C practice.