empty object should be an identity type relative to the intersection operation

[zpdDG4gta8XKpMCd]

type T = {} & { value: 1 } // expected to be { value: 1 }, actual { value: 1 } & {}

[RyanCavanaugh]

What's the observable effect of this? Other than the string representation looking weirdish

[zpdDG4gta8XKpMCd]

none

…

On Mar 21, 2017 3:40 PM, "Ryan Cavanaugh" ***@***.***> wrote: What's the observable effect of this? Other than the string representation looking weirdish — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#14762 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA5Pzb1db8lW-wPs-60v6Xz7lrzuWUZpks5roCePgaJpZM4Mjua-> .

[RyanCavanaugh]

Seems like we should just special case it out of & in typeToString

[zpdDG4gta8XKpMCd]

just checked the latest nightly version, still see it:

[RyanCavanaugh]

We can remove this during createIntersectionType as long as at least one of the other constituents is objectlike (thus there would be no effects of having it in the intersection). Types like string & { } are still distinct from string so will need to keep { } in the intersection