leanprover-community / leanprover-community/mathlib4

Porting note: broken ext

Open
#11,041 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

porting-notes
Dominant language
Lean
Stars
4.1k
Forks
1.7k
No merged PRs in 30d

Description

Classifies porting notes claiming anything equivalent to:

  • "broken ext"
  • "was ext"
  • "used to be ext"
  • "ext fails"
  • "was ext in lean 3"
Links
  • #11182: categorises removed @[ext].
  • #5229: categorises adding ext lemmas.
Examples

https://github.com/leanprover-community/mathlib4/blob/f5e8fa18d5a94db4a55b0ff392e1041baf731c4f/Mathlib/Algebra/Category/ModuleCat/Adjunctions.lean#L186-L216

https://github.com/leanprover-community/mathlib4/blob/f5e8fa18d5a94db4a55b0ff392e1041baf731c4f/Mathlib/Algebra/Category/ModuleCat/Monoidal/Basic.lean#L179-L191

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

Read the two linked example sections in Mathlib/Algebra/Category/ModuleCat/Adjunctions.lean and Mathlib/Algebra/Category/ModuleCat/Monoidal/Basic.lean, then review issues #11182 and #5229 for the surrounding categorization. Done should be a consistent classification for porting notes about broken or formerly available ext behavior.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, tooling
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.