ruby-dirty-memoize 0.0.4-1.1 source package in Ubuntu
Changelog
ruby-dirty-memoize (0.0.4-1.1) unstable; urgency=medium * Non maintainer upload by the Reproducible Builds team. * No source change upload to rebuild on buildd with .buildinfo files. -- Holger Levsen <email address hidden> Sat, 09 Jan 2021 16:27:45 +0100
Upload details
- Uploaded by:
- Debian Ruby Extras Maintainers
- Uploaded to:
- Sid
- Original maintainer:
- Debian Ruby Extras Maintainers
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| ruby-dirty-memoize_0.0.4-1.1.dsc | 2.1 KiB | b1b5bcb9bf928e0aef75e8ff9d239e50f06604d26f4c03e17fab9d3ba59ac128 |
| ruby-dirty-memoize_0.0.4.orig.tar.gz | 6.2 KiB | 60fc15f23e446da2ac511dba8efca62e04699f8e40a10c849d0c8300073e2068 |
| ruby-dirty-memoize_0.0.4-1.1.debian.tar.xz | 2.3 KiB | c64663c9140b6b3dbb5dcc45d8e9109c48525dbe2b8d09e17b1863ec3624e13a |
Available diffs
- diff from 0.0.4-1 to 0.0.4-1.1 (380 bytes)
No changes file available.
Binary packages built by this source
- ruby-dirty-memoize: Similar to ruby-memoize, but for mutable and parameterizable objects
The dirty-memoize library can help making your program faster in the
following cases:
.
- You have one expensive method which sets many internal variables,
thus lazy evaluation of these dependent variables is preferred.
- The expensive operation depends on one or more parameters
- Changes to one or more parameters affect all dependent variables
- You may want to hide the call to the 'compute' operation
