Hacker News Reader

Comment by monster_truck | Hacker News Reader

It's had return type declarations since 7. There's even intersection and literal types now. You could have typed this into google and it would have told you

View on HN

I did and it told me that it doesn't support typed arrays.

Man that goal post moved quick.

The example on the Psalm 7 page (https://psalm.dev/) showed the PHPDoc return type.

I was not precise enough about the exact version of it, fair, but my correction did not change my opinion on this topic.

And the PHPDoc stuff is old, it was normal to write them everywere 11 years ago and still today you have to write them for some cases.

Its still inconsistent and stupid.

Type declarations are still quite limited, though. For example, you can declare that a function returns an array or a string, but not an array of strings.

Use a class if you need them.

How does that solve the problem? You can't declare an array of strings inside a class, either.

You can annotate the method as `@return array<array-key,string>` or even `@return list<string>` (array of strings = indexed via anything that can be used as a key in PHP vs list of strings = indexed via incrementing integers, starting from 0). I guess the OP suggestion was to use Arrayable / Iterable interfaces, which would work as well, but would require more effort (= yes, declare a class)

Do some research :D.

Just to be clear, you suggest to wrap a typed array into its own class? is that the suggestion you think of?

Because if yes, thats just ugly and a hack/workaround.

Reply on news.ycombinator.com