Rename `Parallel` => `ParBeta` or `FullBeta.Parallel`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- compilers
Research direction
Start with the Parallel relation in the linked FullBetaConfluence API documentation and review the parallel β-reduction changes from #965. Trace where the relation and its ⭢ₚ notation are defined and used. Done means the β-reduction name is unambiguous and the notation plan distinguishes it from parallel η-reduction.
Written by the indexing model from the issue text.
Description
#965 introduces parallel η-reduction. As a result, Parallel is no longer an unambiguous name for the parallel β-reduction, since we will now have both parallel β-reduction and parallel η-reduction.
The parallel β-reduction is currently defined as Parallel.
I suggest renaming Parallel to either ParBeta or FullBeta.Parallel. This would make it clear that the relation specifically represents parallel β-reduction.
There is also a notation issue. Parallel currently uses the notation ⭢ₚ. If ParEta is introduced for parallel η-reduction, it is unclear what notation should be assigned to it.
- Dominant language
- Lean
- Stars
- 771
- Forks
- 216
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 116
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from leanprover/cslib
-
`listFullBeta_cons_r` should rename to `listFullBeta_concat_r`Possibly taken @lengyijun claimed this 103 days ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 72/100
leanprover/cslib#784 ·
Maintainers usually reply within 1 day
-
logic
Difficulty 1/5 Under an hour Newbie friendliness 72/100
leanprover/cslib#74 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 28/100
leanprover/cslib#1144 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
leanprover/cslib#824 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 64/100
leanprover/cslib#823 ·
Maintainers usually reply within 1 day
All issues in leanprover/cslib
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rescript-lang/rescript#8996 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug P2
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
duplicate
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
numba/numba#10939 · 1 comment ·
Maintainers usually reply within 1 day