Larry Garfield

Hrm. I think the original logic from the spec authors was along the lines of "all cache writes are independent of each other. The existence of a previous record is...

I think we can update the docblock in the actual package. We've tweaked those as part of the type updates before. I am not sure if updating the spec proper...

I've only ever seen it without a space: `(int)$x`.

If that's the de facto consensus, I don't have a strong argument to not follow it on this one. Sounds like we need a PR.

We deliberately excluded those characters because we expected them to be the most likely to be used in future PSRs extending PSR6, such as a namespacing PSR or a cache-tags...

Waiting for someone to do the research on this. I don't have the bandwidth to do so: > Are there similar patterns in other cache backends? IMO, if we're going...

I will also note that there is a fair number of anecdotal statements about tabs being better for accessibility, but I am not aware of any actual research or verification...

I've run into this parser issue as well. At its root it's a PHP-Parser bug, but even that aside it's the sort of arbitrary thing worth trying to standardize.

The PR in #26 makes it clear that no blank line is permitted.

I'll note that, if a template engine wants to have extra/standard/default stuff, it can always implement PSR-14 internally to pass the context set to listeners that can set default values...