... | ... | @@ -2,15 +2,16 @@ |
|
|
|
|
|
I move stuff here from the different sections that is on our radar at the moment.
|
|
|
|
|
|
- #20111, !6168: Bug in `exprMightThrowPreciseException`
|
|
|
- Morally, we need a new `primOpHasExternallyVisibleSideEffects`. But that's a huge time sink with large potential for regression (#17653)
|
|
|
- So just add `CatchOp` to "the list" for now?
|
|
|
- #19970, #20269, #20273: Floating case expressions, related to `Note [Case MFEs]`
|
|
|
- In general it seems like non-cheap case scrutinees get in the way of eta-expanding PAPs
|
|
|
- #19871, !5790 boxity analysis. See also https://gitlab.haskell.org/ghc/ghc/-/issues/19824#note_353112
|
|
|
- Nice idea for a paper: DmdAnal, (then termination analysis,) then Boxity analysis, which infers boxity for parameters and results.
|
|
|
- !5667: Nested CPR light, part 2
|
|
|
- #5075, !4229: CPR for sum types
|
|
|
- Nearly no regressions after !5667 and simpler analysis code
|
|
|
- #20111, !6168: Bug in `exprMightThrowPreciseException`
|
|
|
- Morally, we need a new `primOpHasExternallyVisibleSideEffects`. But that's a huge time sink with large potential for regression (#17653)
|
|
|
- So just add `CatchOp` to "the list" for now?
|
|
|
- #19001, #19970: Floating case expressions, realted to `Note [Case MFEs]`
|
|
|
- #14816, !5349: Drop `reuseEnv` in DmdAnal
|
|
|
- I got hung up on improving efficiency of fixed-point iteration which got more costly as a result. Should we worry? Maybe add GHC.Ix as a regression test and be done with it
|
|
|
- #19584: Demand Analysis scales quadratically
|
... | ... | @@ -179,4 +180,4 @@ I move stuff here from the different sections that is on our radar at the moment |
|
|
- Why? What's needed? A formal Specification? Which part? Static or dynamic semantics?
|
|
|
- Also how much? Whole pattern language or just enough of a fragment to explain or patterns?
|
|
|
- I see there is https://gitlab.haskell.org/rae/haskell as a starting point, but it seems to focus entirely on static semantics. But probably the document to complete?
|
|
|
- We talked about it; it's a matter of pushing the proposal forward rather than investing actual elbow grease into an impl. |
|
|
\ No newline at end of file |
|
|
- We talked about it; it's a matter of pushing the proposal forward rather than investing actual elbow grease into an impl. |