Should we seal `FileExt`, `MetadataExt` and `OpenOptionsExt`?
Open
Nobody has claimed this yet.
C-discussion
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
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 linked discussion in issue #118795, especially the referenced comment, to understand the proposal for sealing FileExt, MetadataExt, and OpenOptionsExt. The issue itself names no files, tests, or settled acceptance criteria; done would require an agreed API-design decision and its implementation plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100