not really known
Go to file
2024-08-13 08:36:20 +00:00
.github/workflows Enable ghc-9.10 on CI 2024-07-29 07:53:56 +02:00
scripts Added check-changelogs.sh script to CI 2023-07-28 13:12:22 +02:00
src/NoThunks Report _both_ context _and_ info 2024-08-08 10:40:41 +02:00
test Report _both_ context _and_ info 2024-08-08 10:40:41 +02:00
.gitignore Initial version 2020-09-09 17:30:43 +02:00
cabal.project Upgrade to GHC 9.8: bump dependencies, fix testsuite, CHANGELOG 2023-10-28 19:50:25 +02:00
CHANGELOG.md nothunks-0.3.0.0 2024-08-13 10:03:04 +02:00
LICENSE Changed LICENSE to Apache-2.0 2023-03-30 18:30:08 +02:00
nothunks.cabal nothunks-0.3.0.0 2024-08-13 10:03:04 +02:00
NOTICE Updated cabal & NOTICE files 2024-01-02 13:02:49 +01:00
README.md Use wherefrom-compat 2024-02-03 19:01:17 +00:00

nothunks

CI Tests

Long lived application data typically should not contain any thunks. This library can be used to examine values for unexpected thunks, which can then be used in assertions. This can be invaluable in avoiding memory leaks, or tracking down existing ones.

See my presentation MuniHac 2020: Being lazy without being bloated for an overview, motivating the library and explaining how it is intended to be used and how it works internally.

nothunks will try to get source information from info tables. For that one needs to use GHC 9.2 or newer and compile the code with -finfo-table-map. More precise information will be available if -fdistinct-constructor-tables flag is used as well.