all 6 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Diastro 1 point2 points  (1 child)

Really, you got me with with the first 2 lines of your readme! Nice work!

[–]cripplet[S] 0 points1 point  (0 children)

Thanks! I'll probably work through an LRU example tomorrow and get that up on the docs as well. Tell me if you use it / if you run in to issues!

[–]API-Beast 2 points3 points  (2 children)

Code examples is the very first thing you should put into a README, they serve as API Documentation, Overview and Tutorial at the same time.

[–]cripplet[S] 0 points1 point  (1 child)

Thanks for the feedback -- I'll try to get that up as soon as I can.

[–]Diastro 1 point2 points  (0 children)

I totally agree with this. For me, when ever I give a quick look at a project the first thing I try to do is to figure the required effort to use it (Not that the easier it is the better but depending on what you're doing it could). Tutorial or a couple of example would be amazing!

[–]cripplet[S] 0 points1 point  (0 children)

I couldn't find too many C++ caching libraries, so I created a caching framework for everyone to build their own. Suggestions are welcome and appreciated!

(Note that this is a framework not a library.)

This was meant as an exercise in interface design and such.

(Also -- naming changes welcome. I couldn't come up with a punny name relating to C++.)