leanprover-community / leanprover-community/mathlib4
Lindelöf and paracompact spaces
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 4.2k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Inspired by PR #7160. Here are some possible steps, non-exhaustive :-)
Lindelöf spaces
- definition (every open cover has a countable subcover)
- #9168
- $\sigma$-compact spaces are Lindelöf
- basic properties: countable unions, images of Lindelöf sets and spaces are Lindelöf
- follow-up: adapt e.g.
CompactExhaustion.choiceto ask for Lindelöf instead; audit comments mentioning "Lindelöf"
extension: hereditarily Lindelöf spaces
- definition: every subspace is Lindelöf (see pi-base)
- Lindelöf implies hereditarily Lindelöf
- a Lindelöf $G_\delta$ space is hereditarily Lindelöf
- secound countable implies hereditarily Lindelöf
Paracompact spaces
- definition
- locally compact and sigma-compact spaces are paracompact,
in particular compact spaces are paracompact - every metric space is paracompact
Corollary of both: a locally compact second countable Hausdorff space is paracompact.
Lots of potential for extensions, e.g.
- locally compact + second countable implies $\sigma$-compact
- show these notions coincide over metric spaces
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
Start by reading the existing topology material referenced in Mathlib/Topology/Paracompact.html and Mathlib/Topology/SubsetProperties.html, then inspect CompactExhaustion.choice for the Lindelöf follow-up. Choose one unchecked item, such as the Lindelöf Gδ result or the metric-space equivalence, and confirm its assumptions and nearby theorem style. Done means the selected result is formalized with appropriate supporting updates.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100