parcel-bundler / parcel-bundler/lightningcss
Add "owned" error types
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.7k
- Forks
- 302
- PR merge metrics
- No merged PRs in 30d
Description
Currently many error types are have attached lifetimes. This means they can not be boxed and bubbled up. It'd be great if errors were fully "owned", and did not have attached lifetimes. I don't think this should be super terrible for perf, as errors are usually very much an edge case.
The bigger question is: how could this be done?
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
The issue names no files, tests, or entry points. Start by locating the error types with attached lifetimes and tracing where they are created and propagated. Done means determining and implementing a design that makes those errors fully owned so they can be boxed and bubbled up without attached lifetimes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100