Reconsider match_byte macro if plain match becomes optimized enough
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 869
- Forks
- 152
- Avg merge
- 15h 8m
- Merged PRs (30d)
- 12
Description
@nox pointed out (https://github.com/servo/rust-cssparser/pull/112#issuecomment-286152329) that https://github.com/rust-lang/rust/pull/39456 brings the same performance to plain match expressions.
Contributor guide
No contributing guide indexed for this repository
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 locating the match_byte macro and review the linked Rust and Servo pull requests to understand the optimization claim. Benchmark plain match against the macro in the affected parser paths; done means the evidence supports replacing or retaining the macro and the issue's decision is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- web-dev
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100