Hi, you don't "need" this stub for phpstan/phpstan-symfony#92, you can go on and use just SplObjectStorage<MutableAclInterface> in there. You're right, this would be a BC break, better to target 1.0 with this.

And fix the stub by looking at the build log :)

Hi, you don't "need" this stub for phpstan/phpstan-symfony#92, you can go on and use just SplObjectStorage<MutableAclInterface> in there.

Currently it's only possible to set the keys, not the values.
So I could write SplObjectStorage<ObjectIdentityInterface> indeed.

You're right, this would be a BC break, better to target 1.0 with this.

When using array, we can either write array<Value> or array<Key, Value>.

A BC way would be to allow SplObjectStorage<Key> and SplObjectStorage<Key, Value>.
But I don't know how to write this. And I'm not sure it's a good idea, since it's not consistent with array.

Why target 1.0 ? Breaking changes are allowed in a 0.x version. It could be 0.13.

And fix the stub by looking at the build log :)

Sure, but the errors are not really clear to me.
If I understand correctly I should keep the functionMap definition.

The next major is going to be 1.0, not 0.13 :)

It's a BC break because on level 6 there's going to be a new error message because SplObjectStorage becomes generic.

The next major is going to be 1.0, not 0.13 :)

It's a BC break because on level 6 there's going to be a new error message because SplObjectStorage becomes generic.

Ok !

Any idea about the build failure ?

interface does not implement other interfaces, it extends them. You can also run vendor/bin/phing phpstan lcoally for faster feedback.

Sure, thanks. I'll make a note to merge this once 1.0-dev is opened.

Sure, thanks. I'll make a note to merge this once 1.0-dev is opened.

I'm curious, any release-goal for the 1.0 version ?

Do you mean a date? Winter 2020-21. So in around 6 months.

It's a BC break because on level 6 there's going to be a new error message because SplObjectStorage becomes generic.

I thought about this.
I find kinda sad that every new generic class will be a BC break.

The following class could be generics: SplPriorityQueue, SplMinHeap, SplMaxHeap, SplHeap, SplQueue, SplStack, SplDoublyLinkedList. I'm sure there is (lot of) others.
Either you'll need to often release major, either people will need to wait for this kind of feature.

What is the name of the rule which will fail ?
Maybe a exclude param could be useful.

When you introduce a generic, you'll had to the exclude list

genericRule: true
genericRuleExcluded:
    - SplObjectStorage

And then, in the next major, you remove it from the exclude list.

WDYT ?

I've thought about this - we could add these new stubs in bleedingEdge.neon and that would be fine by me.

Thank you!