Joachim Breitner

> I'm surprised GHC can still optimize these sufficiently for inspection-testing to see that they are the same. There isn’t anything to optimize: They are already just the same (up-to...

> That requires some inductive reasoning that seems to fit in the scope of ghc-proofs. Not sure if inductive reasoning really fits the scope of `ghc-proofs`: The idea of `ghc-proofs`...

Well, hiding the AE label will fix the problem of unnecessary scrolling. The refreshing of the actual screen from the HDMI is of course out of FreeDcam’s control and unavoidable,...

Maybe update the hackage metadata at https://hackage.haskell.org/package/row-types (or simply make a new release)?

This might also alleviate the concerns in https://github.com/repology/repology-updater/issues/638 a bit.

At least in the case of Haskell packages, the “sources” are auto-generated from Hackage, so there are 10000 packages reported as present that nobody ever built, let alone manually touched....

> rather it should be handled differently and on a global level. That sounds good as well, of course. What do you have in mind?

If we ever get to this, maybe there is a variant where array setting could look like ``` do a[i] := x ``` or similarly slick.

The latest version of `gitSource.nix` that I am using here internally has this logic to handle worktrees: ``` git_dir = if builtins.pathExists ../.git/index then ../.git else # likely a git...

I guess that’s true. Patch is welcome :-)