| 21 Jul 2025 |
 maralorn | Maybe the even appear somewhere in the build log, e.g. in the configureFlags, although I am not sure about that. | 10:03:23 |
 magic_rb | hm, i could swear it made a difference when i was developing this thing, idk why the performance difference vanished, now it doesnt really matter what flags i use | 10:03:47 |
| magic_rb | fun, my thesis is gonna be "well, these did something when i was writing this, now they seemingly dont anymore. IDFK why, future work" | 10:05:12 |
| maralorn | Did you maybe apply expose-all-unfoldings to dependencies as well? That might make a difference. | 10:07:42 |
| magic_rb | not that im aware of | 10:08:10 |
| magic_rb | ghc-options: -Wall -threaded -O2 -fllvm -Wno-unrecognised-pragmas -fspecialise-aggressively -fexpose-all-unfoldings
on my library and executables | 10:08:23 |
| magic_rb | but not in cabal.project | 10:08:29 |
| magic_rb | and when i was profiling this back then, most of the slowness was in my code because of my custom monad transformer | 10:09:04 |
| magic_rb | im gonna remove the inline pragmas, those didnt seem to be enough last time i tried, which is why i enabled -fexpose-all-unfoldings | 10:10:29 |
| magic_rb | but ill try to removing them again and see if some difference shows up | 10:10:42 |
| magic_rb | okay, same result, im completely confused and have no clue what is going on | 10:19:40 |
| maralorn | I mean, is it a different ghc version than when you added those flags? | 10:20:28 |
