Dave Marshall

It's not ideal, but you can call the constructor manually? ``` php class Dave { public function __construct() { $this->foo(); } public function foo() {} } $m = Mockery::mock(Dave::class)->makePartial(); $m->shouldReceive()->foo()->once();...

Not sure on this one. It works in practice, but only because you usually receive a `CompositeExpectation` from `Mock::shouldReceive`. `CompositeExpectation` has the `__call` to pass unknown calls back to the...

I thought so, I think we nailed everything...

I think I'm with @zombor, what sort of scenarios would we need to mock an iterator, e.g. when a fake wont do the job?

> A con with this current implementation is that the array items can't be updated. I.e. it does not stub `ArrayAccess::offsetSet()` and `ArrayAccess::offsetUnset()` Is this a limitation of Mockery or...

I think that's likely :+1:

Another issue raised: #1037

Nice! Do you think we need to hold on this one until 2.0 though? Are we going to get loads of people complaining that we broke their suite with loads...

Honestly, I've no idea. I've only really recently started using intelephense and I've no idea how the phpstorm meta works, I've just been led by people who use it :shrug:.

The config remains that way until you set it back I believe.