Do not create a throw point for void returned by dynamic throw type extensions

[ondrejmirtes]

Returning VoidType from a DynamicFunctionThrowTypeExtension, DynamicMethodThrowTypeExtension or DynamicStaticMethodThrowTypeExtension (also for new) created an explicit throw point of type void, instead of saying that the call does not throw. As a result:

• a variable assigned in the try block was only maybe-defined in finally,
• catch (\Throwable $e) around the call was not reported as dead,
• a function with @throws void calling it was reported with throws exception void but the PHPDoc contains @throws void,
• custom rules that look at explicit throw points ($throwPoint->isExplicit()) saw a throw.

Ds\Map::get() / remove() with a default value (DsMapDynamicMethodThrowTypeExtension) are affected today.

A @throws void declaration without an extension already produces no throw point (FuncCallHandler::getFunctionThrowPoint() skips it when $throwType->isVoid()->yes()). This PR does the same in the extension branches of FuncCallHandler, MethodThrowPointHelper and NewHandler.

This is groundwork for the upcoming throw type extensions for functions that PhpStorm stubs now declare as throwing ValueError and similar (min()/max(), sprintf(), ...). They will return VoidType when the call cannot throw.

Tests:

• DynamicMethodThrowTypeExtensionTest with new test extensions returning VoidType for a function, a method, a static method and a constructor (variable certainty in finally)
• CatchWithUnthrownExceptionRuleTest::testDsMapVoidThrowType() for the real Ds\Map extension

Both fail without the change.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Dhb4ssXuKVWcVBcNFpsdn7