Skip to content

[Chore] Improve morley compilation time

Description

Improve compilation time on morley. Part 1 definitely improves things. Part 2, I'm not exactly convinced by. In my initial investigation, it seemed to save quite a bit of time (around 25-30 seconds), but after tweaking Part 1 it's pretty close to the margin of error. UPD: after some more testing, the cost is around 10 seconds for morley on my machine. Which doesn't seem like much, but little things like this tend to add up. OTOH, if we don't care about this, I would suggest getting rid of DeMorganScope by putting constraints on parts of the type into the superclass of ForbidT. This will cost us around another 10 seconds (as measured on my machine).

Some concrete numbers from CI:

Related issue(s)

Resolves None. I could create an issue, but that seems kinda pointless.

Checklist for your Merge Request

Related changes (conditional)

  • Tests (see short guidelines)

    • If I added new functionality, I added tests covering it.
    • If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again.
  • Documentation

    • I checked whether I should update the docs and did so if necessary:
    • I updated changelog files of all affected packages released to Hackage if my changes are externally visible.

Stylistic guide (mandatory)

Edited by Nikolay Yakimov

Merge request reports