lean-ja / lean-ja/lean-by-example

型強制は常に単射であるべき?

Open
#2,505 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Zulipで質問すべき
Dominant language
Lean
Stars
188
Forks
15
Avg merge
9h 8m
Merged PRs (30d)
6

Description

たとえば String → Bool を「空なら false で空でないなら true 」と設定すると単射にならない。ユーザーが困惑したりバグの原因になったりする可能性が高く、これは型強制として設定するべきではないだろう。

Coe のドキュメントコメントに追記してもよいレベルで、これは推奨されることなのだろうか?

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 reading the existing Coe documentation comments and the surrounding guidance on type coercions. Determine whether the injectivity concern warrants an explicit recommendation, then document the agreed guidance in the appropriate Coe comment; done means the recommendation and its rationale are clear to users.

Written by the indexing model from the issue text.

Assessment

Domain
compilers
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.