Simon Marlow

This pull request adds `hsc2hs-options`: https://github.com/haskell/cabal/pull/6295

I actually use `ghc` as the linker for hsc2hs (see https://github.com/simonmar/cabal/commit/c2ff41c45e91346ef8251665cd20bceebb511c2a). It's possible I could also use `-pgml g++`, but I think I found that `-lstdc++` worked fine, so I...

I'm not convinced by this. Strategies are supposed to do evaluation *only*, and it's pretty clear that a strategy that returns a different type is doing more than evaluation! Moreover,...

This is a very old library with some historical decisions that we would probably make differently today. `Strategy` being a type synonym rather than a `newtype` is one of those...

I think I understand your point that there are useful strategies you can write with this that you couldn't before, and that some things work out more nicely. However, there...

Great. Can we have some tests and benchmarks please?

I don't actually know how to update the docs on `haskell.org` these days. If anyone could help with this I'd be grateful - @bgamari perhaps?

ghc-events was specifically designed to be forwards and backwards compatible as far as possible. Otherwise, you have to build a specific ThreadScope binary that works with the version of GHC...

Oh, and BTW testing support for old versions really just means keeping around old eventlog files, we don't necessarily need access to a working GHC.

> So how do we reconcile this: Unfortunately there's a cost to backwards compatibility, and in this case it's the extra work in maintaining the library that works with multiple...