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

参照カウントが1を超えており破壊的に更新できていない箇所を指摘するリンター

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

Nobody has claimed this yet.

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

Description

静的に指摘することはおそらく可能だと思う。完全である必要もない。

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 locating the repository's existing linter or static-analysis entry point; the issue names no files or tests. Define which cases of reference counts above one should be detected and what destructive update means, then add focused tests showing the warning and its accepted limits.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.