Skip to content
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

Proofreading of YARD docs needed #134

Closed
6 tasks done
alexdowad opened this issue Aug 29, 2014 · 8 comments
Closed
6 tasks done

Proofreading of YARD docs needed #134

alexdowad opened this issue Aug 29, 2014 · 8 comments

Comments

@alexdowad
Copy link
Contributor

The newly written YARD documentation needs a second person to proofread. Check that the docs are:

  • Accurate (if they don't match the actual method behavior, either the docs or the method itself could be buggy)
  • Reasonably complete, without belaboring details too much (what users need to know should be there)
  • Reasonably easy to understand

This could be done either by reviewing the output of YARD, or by reading the embedded docs directly in the source code.

  • Hash
  • Set
  • Vector
  • SortedSet
  • List
  • Deque
@xaviershay
Copy link
Contributor

Link to online reading: http://www.rubydoc.info/github/hamstergem/hamster/master/Hamster

I'm having a go at this.

@xaviershay
Copy link
Contributor

Why are Hash#put and Hash#store not aliases of one another? Seems weird to have both, but maybe that's backwards compat?

@alexdowad
Copy link
Contributor Author

@xaviershay, you're right, there is no reason why Hash#put and Hash#store should not be aliases. To provide some background, #store was added to make the interface of Hamster::Hash match that of Ruby's built-in Hash. #put is common to all the Hamster collections.

Any chances of sending a PR for this one?

@alexdowad
Copy link
Contributor Author

I just pushed a fix for the YARD docs for Hamster.replicate, you may want to pull before continuing your review.

@xaviershay
Copy link
Contributor

thanks for background. Could send PR, but if store is supposed to match Ruby interface then maybe I'll just document it as such. Hoping to get a once over of all the Hash docs done today - will send that up and if you like it I can tackle the rest.

@xaviershay
Copy link
Contributor

Will probably make a different issue for this, but given we are making performance claims ("At the same time, they remain CPU and memory-efficient by sharing between copies.") would probably be good to include expected operation cost in the YARD docs (O(1), O(n), etc). This is a thing I like about the redis docs.

@alexdowad
Copy link
Contributor Author

"Include expected operation cost..."

Hmm, sounds like a good idea.

This was referenced Aug 15, 2015
@alexdowad
Copy link
Contributor Author

@xaviershay, thanks for proofreading ALL the docs for the entire project! It is impressive to see how much better you made them!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants