Title: Case decision tree: MatchHistory prunes only constructor tests — extend to literal patterns and accumulate negatives · Issue #184 · purescript-lua/purescript-lua · GitHub
Open Graph Title: Case decision tree: MatchHistory prunes only constructor tests — extend to literal patterns and accumulate negatives · Issue #184 · purescript-lua/purescript-lua
X Title: Case decision tree: MatchHistory prunes only constructor tests — extend to literal patterns and accumulate negatives · Issue #184 · purescript-lua/purescript-lua
Description: Problem The CoreFn case compiler is already a decision-tree compiler with redundant-test pruning (Note [Compiling case expressions to decision trees], MatchHistory), but the history only covers PatCtor: constructor patterns consult it be...
Open Graph Description: Problem The CoreFn case compiler is already a decision-tree compiler with redundant-test pruning (Note [Compiling case expressions to decision trees], MatchHistory), but the history only covers Pat...
X Description: Problem The CoreFn case compiler is already a decision-tree compiler with redundant-test pruning (Note [Compiling case expressions to decision trees], MatchHistory), but the history only covers Pat...
Opengraph URL: https://github.com/purescript-lua/purescript-lua/issues/184
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Case decision tree: MatchHistory prunes only constructor tests — extend to literal patterns and accumulate negatives","articleBody":"## Problem\n\nThe CoreFn case compiler is already a decision-tree compiler with redundant-test pruning (Note [Compiling case expressions to decision trees], `MatchHistory`), but the history only covers `PatCtor`: constructor patterns consult it before emitting a tag test, while every literal pattern — `PatInteger`, `PatString`, `PatBoolean`, `PatChar`, `PatFloating`, `PatArrayLength` — emits its `eq` test unconditionally, recording nothing (`IR.hs` mkClause: the literal arms vs the PatCtor arm).\n\nRepro: `Data.String.CodePoints.codePointAt` (clauses `codePointAt 0 \"\" = …` / `codePointAt 0 s = …`). Clause 2 tests `0 == v`, fails on its second pattern, falls through to clause 3 — which re-tests `0 == v` although the answer is known in both branches. The compiled golden shows the redundant nested test with a dead `then` branch in the `else` arm.\n\nA second, related gap: the history holds a single slot per scrutinee (`Map Exp (CtorName, Bool)`), so negative knowledge does not accumulate — after `A` fails and `B` fails, the record about `A` is overwritten, and pruning is lossy for sum types with three or more constructors.\n\n## Approach\n\nExtend `MatchHistory` to literal tests with mutual-exclusivity semantics, same as constructors: after a positive `v == 0`, a repeated `v == 0` prunes to success and `v == 1` prunes to failure; after a negative `v == 0`, a repeated `v == 0` prunes to failure and `v == 1` is unknown and gets emitted. Generalize the store from one slot to accumulated knowledge per scrutinee (`Map Exp (Map Tested Bool)`), fixing the lossy-negatives limitation in the same move.\n\n## Prerequisites / Relations\n\nNo prerequisites; independent in the dependency graph. Relates to #172, which would register the code-size reduction. The out-of-scope future work below notes an interaction with the #178/#179/#180 inlining cascades, but this issue does not depend on them.\n\n## Verification / Measurement\n\nThe redundant `0 == v` retest in `Data.String.CodePoints.codePointAt` (clause 3 re-testing what clause 2 already decided) disappears: the golden no longer shows the nested test with a dead `then` branch in the `else` arm. For sum types with three or more constructors, accumulated negative knowledge prunes the now-known tag retests that the single-slot history used to re-emit. Code-size effect tracked by #172.\n\n## Future work (out of scope here)\n\nRedundancy the case compiler cannot see and therefore cannot prune: conditions already established around code spliced in by the inlining cascades (#178, #179, #180), repeated tests across separate case expressions on the same scrutinee (history lives within one `mkCase`), and guard expressions. If #172 shows these matter in practice, a separate IR-level predicate-propagation pass picks them up; until then this issue covers the observed cases.\n","author":{"url":"https://github.com/Unisay","@type":"Person","name":"Unisay"},"datePublished":"2026-07-06T10:48:18Z","url":"https://github.com/purescript-lua/purescript-lua/issues/184"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:0d074fe5-69b4-82f6-d954-7bf2e550a116 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | A58C:EA06E:9F03F0:CE161C:6B00DFC1 |
| html-safe-nonce | 32d55a210c84da0cf612642e0d2930e8600a8b90a751bcd4990f3c1ac7e5e841 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBNThDOkVBMDZFOjlGMDNGMDpDRTE2MUM6NkIwMERGQzEiLCJ2aXNpdG9yX2lkIjoiMTIzMjY3NzU1MDE0NTIwMDA2NSIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | f863bca95103dcb9138ab7a778cf84c6d2325c10dee158f678304007b35f7230 |
| hovercard-subject-tag | issue:4818376609 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/purescript-lua/purescript-lua/184/issue_layout |
| twitter:image | https://opengraph.githubassets.com/3ca5d65fbdc6c2b265b0deb063728fa53dc046d550aef87492b2fcc35ead5cac/purescript-lua/purescript-lua/issues/184 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/3ca5d65fbdc6c2b265b0deb063728fa53dc046d550aef87492b2fcc35ead5cac/purescript-lua/purescript-lua/issues/184 |
| og:image:alt | Problem The CoreFn case compiler is already a decision-tree compiler with redundant-test pruning (Note [Compiling case expressions to decision trees], MatchHistory), but the history only covers Pat... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | Unisay |
| hostname | github.com |
| expected-hostname | github.com |
| None | 043c3f30fbcbe2c6c8e729e10cbbbc90c406546f9fbbb67c648d38f6b7d16daf |
| turbo-cache-control | no-preview |
| go-import | github.com/purescript-lua/purescript-lua git https://github.com/purescript-lua/purescript-lua.git |
| octolytics-dimension-user_id | 131581790 |
| octolytics-dimension-user_login | purescript-lua |
| octolytics-dimension-repository_id | 587200487 |
| octolytics-dimension-repository_nwo | purescript-lua/purescript-lua |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 587200487 |
| octolytics-dimension-repository_network_root_nwo | purescript-lua/purescript-lua |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 5425dc24e8bd8d6fca9641a12afc984825a43875 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width