René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"rfc recursive return type definitions","articleBody":"```php\r\n/**\r\n* @return array\u003cstring, scalar|array\u003cint, array\u003c{{recursive definition is here}}\u003e\u003e\u003e\r\n*/\r\nfunction DoThingWithNode(DOMNode $node) : array { /* do stuff here */ }\r\n```\r\n\r\nSo I have this method that return an array with string keys whose values are either scalars or arrays with string keys whose values are either scalars or arrays with string keys whose values are either scalars with string keys..... etc.\r\n\r\nIf the definition stops at array, then one would just assume that phpstan et. al would determine that values at that level are \"mixed\" (or otherwise defined), which may be an undesirable effect.\r\n\r\nOne solution to the recursive `@return`/`@param` problem could be to define a class that encapsulates the recursion- i.e. `class Thing extends ArrayObject` \u0026 modify the return types to indicate `scalar|Thing`, but I'd be wanting to avoid class definitions.\r\n\r\nA docblock-type solution would be to define a template/pattern tag so one could `@thing foo array\u003cstring, scalar|array\u003cstring, {{@thing foo}}\u003e` , but I could foresee problems by virtue of it being a recursive solution to a recursive problem.\r\n\r\nThoughts?\r\n\r\np.s. the recursion here comes from the return type possibly containing arrays of the return type of the method, so maybe `@return array\u003cstring, scalar|{{@method DoThingWithNode}}||{{@method DoSomeOtherThingWithNode}}\u003e` might be a solution by explicitly indicating the return values is built up from other methods ?","author":{"url":"https://github.com/SignpostMarv","@type":"Person","name":"SignpostMarv"},"datePublished":"2018-04-01T11:42:44.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/9/phpdoc-parser/issues/9"}