tasty-cache: Nix-style test caching for Haskell
tasty-cache is a Haskell library that enables selective test caching by skipping tests whose source code hasn't changed since the last passing run, using GHC HIE files for precise dependency tracking. It integrates with the Tasty testing framework and allows developers to wrap specific test groups with a cacheable flag for optimal performance. The tool is designed to work safely with pure tests while ensuring effectful tests run unconditionally.
- ▪tasty-cache uses GHC HIE files to track dependencies and determine whether a test should be re-run based on source changes.
- ▪Only tests explicitly wrapped with the cacheable function are subject to caching; others run every time.
- ▪The library requires GHC version 9.4 or higher and emits warnings or falls back to running all tests if HIE files are missing or unreadable.
- ▪It is distributed as a Nix flake with support for multiple GHC versions and integrates into Nix-based development workflows.
- ▪Tests involving side effects, network calls, or external state are intended to remain uncached for correctness and reliability.
Lobsters files mainly under programming. We currently carry 187 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/silky/tasty-cache |
| Publication time | Tue, 28 Apr 2026 08:22:06 -0500 |
| Retrieval time | 2026-04-28T13:24:31.953Z |
| Last seen | 2026-04-28T13:24:31.953Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | ARXTBuyFosMj |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
NoteThis project was built almost entirely with AI; see How this was built for the prompts. A human did, however, read over the readme and find it acceptable. tasty-cache A Tasty ingredient that skips tests whose source hasn't changed since the last passing run, using GHC HIE files for fine-grained dependency tracking. Quick start 1. Emit HIE files — add to both your library and test-suite stanzas in your .cabal file: library -- ... your other fields ... ghc-options: -fwrite-ide-info -hiedir .hie test-suite tests -- ... your other fields ... ghc-options: -fwrite-ide-info -hiedir .hie Both stanzas need these flags because the cache reads the HIE files for your library modules (to follow dependency chains) and your test module (to find the test body source). 2.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.