Larry Garfield

Unfortunately, Closures are not constant expressions so cannot be used as attribute arguments. (I just tested it.) I think this has to be a new property on the Field def.

Fixed in `master`. Not sure when I'll tag a new release. There's a few other outstanding requests I want to get to first, and some test cleanup.

Interesting. I think your compliance officer is being a bit excessive, but I'll bring this up with other FIG members and see what they think, since if we added something...

I disagree with the other PR for unrelated reasons, but this change seems fine.

Looks good to me, but waiting for other WG members to weigh in.

Seems like we should add the same warning to other functions, then. Is it worth making an entity out of it, or just copy-paste-tweak?

What is insufficient is my awareness that entity already exists. :smile: Switched to using that, and added `touch` to the list on the `clearstatcache` page, which was missing.

At present there is no standard, I believe. I've seen people say Internals has one for PHP, but it's not followed consistently. (I forget off hand which way it goes,...

We have no official stance, as a WG or as FIG, on following Internals conventions. Though Internals conventions are indeed one factor we should consider among many.

Update: Internals adopted a standard for new classes in 2017, that uses PascalCase except for Acronyms. https://wiki.php.net/rfc/class-naming So `HTTPStatusCode`, `URL`, `BTreeMap`, etc. It would be logical to follow suit for...