Skip to content

Commit

Permalink
Adding link to the blog post for lru cache
Browse files Browse the repository at this point in the history
  • Loading branch information
Yomguithereal committed Jan 10, 2024
1 parent 0d69bc6 commit a935993
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 0 deletions.
2 changes: 2 additions & 0 deletions lru-cache.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,8 @@ This structure is very useful to cache the result of costly operations when one

For more information, you can check [this](https://en.wikipedia.org/wiki/Cache_replacement_policies#Least_recently_used_(LRU)) Wikipedia page.

For a detailed explanation of how this cache is implemented, you can also read [this](https://yomguithereal.github.io/posts/lru-cache) blog post.

This implementation has been designed to work with a javascript raw object. You can alternatively find an implementation relying on ES6's `Map` object [here]({{ site.baseurl }}/lru-map). Depending on the precise use case (string keys, integer keys etc.), one or the other might be faster depending on js engine magic.

```js
Expand Down
2 changes: 2 additions & 0 deletions lru-map.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,8 @@ This structure is very useful to cache the result of costly operations when one

For more information, you can check [this](https://en.wikipedia.org/wiki/Cache_replacement_policies#Least_recently_used_(LRU)) Wikipedia page.

For a detailed explanation of how this cache is implemented, you can also read [this](https://yomguithereal.github.io/posts/lru-cache) blog post.

This implementation has been designed to work with an ES6 `Map` object. You can alternatively find an implementation relying on a javascript raw object [here]({{ site.baseurl }}/lru-cache). Depending on the precise use case (string keys, integer keys etc.), one or the other might be faster depending on js engine magic.


Expand Down

0 comments on commit a935993

Please sign in to comment.