describe the different cases of algorithms that effectively act as overloads #3683
Description
(extracted from #3627)
The Array constructor, the TypedArray constructors, and the Date constructor each have behaviour that varies dramatically based on the number and/or kinds of their parameters. For algorithms like these that are just a big switch-case at the top level, we continue to feel it is valuable to keep the behaviour unified and described in a single algorithm, but we also think it'd be useful to have a note or other non-normative text that describes the algorithm informally as overloads.