GHC 9.8.1

Woop! My timerfd change is finally out in the wild!<p>This will make it so that (on systems with timerfd) the runtime will no longer have to wait for the next runtime tick before exiting. This saves on average 5 ms per program run, and up to 10 ms for programs with a very short runtime. Not much for server programs with an expected lifetime of days&#x2F;weeks, but potentially quite nice for CLI programs like hledger or for programs that invoke many other Haskell programs.<p>I accidentally discovered this when trying to optimize an Advent of Code problem and couldn&#x27;t get it below 10 ms no matter what I tried. Eventually I discovered that &quot;hello world&quot; also took 10 ms so I assumed it was just runtime startup costs. Decided to look anyway and found out it was actually runtime shutdown costs, where the runtime would `join` the rts &quot;ticker&quot; thread. The ticker thread would only check for a shutdown flag once every loop, so 10 ms with the default settings. Now it can be shut down immediately, which makes small programs much faster.

&gt; I specified text: 2.1 (a number) instead of text: &#x27;2.1&#x27; (a string) - causing Stack to complain vigorously<p>lol, not even Haskell can escape YAML being YAML.

Asking as a Haskell dabbler - why are features like `ExtendedLiterals` behind an opt-in language extension? Why not just turn it on for everyone?

&gt; We would like to thank GitHub, IOG, the Zw3rk stake pool, Well-Typed, Tweag I&#x2F;O, Serokell, Equinix, SimSpace, the Haskell Foundation, and other anonymous contributors whose on-going financial and in-kind support has facilitated GHC maintenance and release management over the years.<p>Is GitHub sponsoring Haskell development? Or is this them providing some free services (e.g. more Runners) because it&#x27;s a large and importans OSS project?

And stack LTS is still on 9.4...