Weird grammar with function types and intersections

For some reason:

`=>` binds tighter than `&` when `&` comes first

```js
type A = boolean & number => void;
declare function a((boolean & number)): void;

(a: A); // ERROR
```

but `&` binds tighter than `=>` when `=>` comes first?

```js
type B = void => boolean & number;
declare function b(void): (boolean & number);

(b: B); // WORKS
```

It seems like it should be more consistent on both sides.