quasicomputational
quasicomputational
Sorry, maybe I've misinterpreted. I thought that it was being suggested that doctest would toggle between `:m` and `:m *` depending on if `-fobject-code` was in play or not. Then,...
Won't passing `-fobject-code` on the command line also affect every module that doctest's invoked on? That is, I don't see why `doctest -fobject-code` with auto-switching would be any faster than...
[cabal-doctest](http://hackage.haskell.org/package/cabal-doctest) does this already. It's a hack but there aren't any non-hacky solutions presently, and it has the high virtue of working like a charm right now and the even...
I'd like to +1 predictability and going with YAML syntax here. Too many corner cases otherwise and I'm sure one would turn around and bite us eventually. One direct change...
Another option: abuse `if true` to get the desired ordering. This is also an effective workaround today!
Here's a variation of the code that tripped me up: ``` when: condition: impl(ghc >= 8.0) ghc-options: -Weverything executable: ghc-options: -Wno-missing-import-lists ``` On GHC 8.0 and 8.2, the arguments that...
The workaround I used was this: ``` when: condition: impl(ghc >= 8.0) ghc-options: -Weverything executable: when: condition: true ghc-options: -Wno-missing-import-lists ``` That gets the expected ordering, and it's purely a...
FTR, this also happens with defaults: ``` $ cat defaults.yaml ghc-options: A when: - condition: True ghc-options: B $ cat package.yaml name: test ghc-options: C when: - condition: True ghc-options:...
RE warning suppression: I think we'd need it, and also it should go in `package.yaml` so that we don't need to teach whatever is driving hpack about it. I don't...