Ryan Chandler
@ryangjchandler.co.uk
Software Engineer. PHP, Laravel, Rust, Go, Swift, the lot.
https://ryangjchandler.co.uk
https://ryangjchandler.co.uk
It's starting to get pretty close to perfect.
August 15, 2025 at 3:50 PM
It's starting to get pretty close to perfect.
I've spent about 10 hours this week rewriting Phiki's tokenizer so that it's more compatible with TextMate grammars.
Safe to say that it's going well so far...
Safe to say that it's going well so far...
August 14, 2025 at 7:01 PM
I've spent about 10 hours this week rewriting Phiki's tokenizer so that it's more compatible with TextMate grammars.
Safe to say that it's going well so far...
Safe to say that it's going well so far...
Little preview of some PXP progress I've made over the last few weeks... 👀
January 13, 2025 at 8:07 PM
Little preview of some PXP progress I've made over the last few weeks... 👀
PXP is also capable of understanding "array shapes", after some parser updates.
Only a few more DocBlock-specific types to go before I _think_ it has full coverage!
Only a few more DocBlock-specific types to go before I _think_ it has full coverage!
December 23, 2024 at 11:23 PM
PXP is also capable of understanding "array shapes", after some parser updates.
Only a few more DocBlock-specific types to go before I _think_ it has full coverage!
Only a few more DocBlock-specific types to go before I _think_ it has full coverage!
Each member in the enum only has a single field, pointing to a separate struct that holds all of the data (see screenshot).
The solution was to just wrap these fields in a Box. They'll be stored on the heap, rather than the stack, but it means that the enum itself will only ever allocate 32 bytes.
The solution was to just wrap these fields in a Box. They'll be stored on the heap, rather than the stack, but it means that the enum itself will only ever allocate 32 bytes.
December 19, 2024 at 1:47 AM
Each member in the enum only has a single field, pointing to a separate struct that holds all of the data (see screenshot).
The solution was to just wrap these fields in a Box. They'll be stored on the heap, rather than the stack, but it means that the enum itself will only ever allocate 32 bytes.
The solution was to just wrap these fields in a Box. They'll be stored on the heap, rather than the stack, but it means that the enum itself will only ever allocate 32 bytes.