According to mypy_primer, this change has no effect on the checked open source code. 🤖🎉

I feel like FloatOrInt and ComplexOrInt would be slightly more approachable names for folks seeing these types pop up in their IDE on-hover? But don't feel strongly

I was thinking about it, but decided against it for two reasons:

• A bit longer and harder to parse visually. And these will be very common type aliases for a while.
• ComplexInt would need to be called ComplexOrFloatOrInt if we go the literal route.

(Also, let's try to get rid of these quickly after introduction – at least in the most commonly used places.)