`filter` chooses wrong type overload when used with `map`. about types HOT 2 CLOSED

Correct that it should prioritize array over object. It's like that for map as well. That fact that it's not is an oversight. I'll get to this as soon as I can

from types.

#106

I realized while fixing this why the overload order is what it is. It's because for filter(pred), if you then pass it a readonly T[], the overload for Record<string, T> actually picks it up for some weird reason, and we were getting incorrect return types for filter(pred)(list). But then you get the opposite problem with pipe(filter(pred))(list), in that it rejects list and wants a dict

Then I remembered we solved this for map or ready by defining list overload at both top and bottom, which makes everything work as expected!

from types.