Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with memoization
Search options questions only
not deleted
user 14237
An optimization technique where function calls are cached to avoid duplicate computations.
12
votes
2
answers
3k
views
Memoizing or caching Bash function results
Update: I've implemented several of the features suggested below and packaged the improved code into a dedicated project: bash-cache.
I display a number of expensive operations in my Bash prompt (e.g …
- 415