lean-ja / lean-ja/lean-by-example
String と Char を分ける理由
Open
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 188
- Forks
- 15
- Avg merge
- 9h 8m
- Merged PRs (30d)
- 6
Description
- 言語実装者としては、それはそう
- ユーザー目線だと、「一文字なのか」を型レベルで表せるのでAPIが明確になる
Contributor 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.
Research direction
The issue gives a Japanese title and two points of rationale but names no file, chapter, or entry point. First locate where String and Char are explained in the repository, then clarify the intended documentation scope and confirm that the explanation should cover both implementation and user-facing API reasons.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100