microsoft / microsoft/tolerant-php-parser
For nodes: avoid defining properties that would be null, arrays with zero or one elements, etc.
Open
Nobody has claimed this yet.
api
performance
- Dominant language
- PHP
- Stars
- 894
- Forks
- 85
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
We should consider better ways to "squash" these constructs for common scenarios to help improve memory usage.
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 file, test, or entry point; start by surveying the node definitions and measuring memory for nodes containing null properties and zero- or one-element arrays. Done means an agreed representation change is implemented for the common cases and its memory impact and parser behavior are validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100