amesgen

> It can be difficult to get all developers on a single release of Ormolu (e.g., users of VSCode apparently have no idea what version they’re using, and no way...

> Thanks, but I'm not actually able to see the version, just the word `ormolu`; none of the plugins are listed with their versions: > > ``` > % haskell-language-server...

Paused ATM: https://github.com/IntersectMBO/ouroboros-consensus/pull/1295#discussion_r1993941375

> How does this scenario work today? > > > * The node's selection advances from era X to era Y. > > * An untagged transaction arrives that is...

A workaround is to add `alex` as a `build-tool-depends` to the local project, but this is certainly not ideal.

Thanks for opening this, the situation around invalid Haddock comments certainly is a bit subtle. > In particular, it's done at the start of lines in the middle of a...

Oh right, I overlooked that. We sometimes escape Haddock-like triggers even if sth is not an invalid Haddock comment: https://github.com/tweag/ormolu/blob/392b2bce17fb0c8895afd5cc619bba39c51b8ea0/src/Ormolu/Parser/CommentStream.hs#L142 Removing this causes test failures, so this was added for...

Sounds sensible! There was this attempt in the past: #896 > Get `treefmt` to call ormolu once per file, in parallel. This would also be perfectly sensible. Just to get...

Hmm :thinking: Might be interesting to run a profiled version of Ormolu to see if there are any pathologies (such as the one that prompted #896), but I assume your...

Thanks for pointing that out, I agree that a user seeing a message that their key is poisoned will likely mean that they assume that there is/was a key in...