mlabs-haskell / mlabs-haskell/lambda-buffers

Compiler: Performance degradation

Open
#76 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

compiler performance
Dominant language
Haskell
Stars
32
Forks
1
PR merge metrics
No merged PRs in 30d

Description

It seems like #75 introduced some performance issues.

lbf-comp -w goldens/good/work-dir -i goldens/good -f goldens/good/LambdaBuffers.lbf

Takes a couple of seconds to finish.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the reported lbf-comp command against goldens/good/work-dir, goldens/good, and goldens/good/LambdaBuffers.lbf, then inspect issue #75 and the compiler changes it introduced. Compare the command's timing with the pre-#75 behavior if available; the regression is addressed when the affected compilation path no longer shows the reported performance degradation.

Written by the indexing model from the issue text.

Assessment

Tech stack
haskell
Domain
compilers, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.