Sara Itani
Sara Itani
Also any suggestions for tools? There's xdebug + webgrind... any other favorite workflows?
Right now, it's fairly obvious where the majority of our memory usage stems from (*ahem PHP objects...*), and we have some ideas on how to cut down on that when...
e.g. right now we test that skipped/missing tokens are properly included in the tree, but we have no tests for the post-parse `getDiagnostics` walk. Thoughts?
This would be simple once #88 is implemented (trailing trivia == leading trivia of the next token)
The API is shifting around quite a bit right now, so this'll help us ensure things stay in sync.
This error tolerance case needs some special handling. ```php class A { function b() { if ($expression { $a = 3; $b = "hello"; } echo "hi"; } public function...
The code below is currently improperly parsed without errors. ```php class A { use \A { \a as b; \b insteadof C; } } ```
The PHP spec was a bit open to interpretation at times, so it'll be good to have a second pass, and should be a good opportunity to add more tests....
We are currently at ~98.5% pass rate on framework validation tests (a test fails if there is an error present in the tree for known valid code). We should inspect...
We should consider better ways to "squash" these constructs for common scenarios to help improve memory usage.