Odd page break in chapter on Monads
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Open book/FPLean/Monads.lean and compare the paragraphs at lines 26–34 and 36–44 in the rendered chapter. Move the first paragraph under “One API, Many Applications” into the chapter description, then verify that the context and explanation flow together without the unwanted page break.
Written by the indexing model from the issue text.
Description
The first two pages of the chapter on monads establish some context by describing related features in other languages:
However, the reader has to wait until the next page to find out why these examples were listed, namely, that these things are related to "monads":
I think that this would flow better if the first paragraph under "One API, Many Applications" were lifted up into the chapter description.
- Dominant language
- Lean
- Stars
- 201
- Forks
- 76
- PR merge metrics
- No merged PRs in 30d
Getting set up
- 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/fp-lean
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
leanprover/fp-lean#304 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
leanprover/fp-lean#301 ·
-
UnusedVariable warning in Point3D pattern matching example (depth function) 1.5.1. Pattern MatchingOpen
Difficulty 1/5 Under an hour Newbie friendliness 90/100
leanprover/fp-lean#298 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
leanprover/fp-lean#296 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
leanprover/fp-lean#291 ·
All issues in leanprover/fp-lean
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
awesome-dsh-plugin/awesome-dsh-plugin#9184 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Lakr233/vphone-cli#738 ·
Maintainers usually reply within 1 day
-
[ordering-review] workshop order graph: 1 confirmed ordering problem, 3 cycles are false positivesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-workshop#4943 ·
Maintainers usually reply within 1 day
-
Awaiting Triage
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100