Please don’t resurrect old threads this way. If you’d like to discuss the topic again, you can start a new thread and summarize the previous discussion for your readers.
To answer your question: This would likely significantly impact type checking performance for arithmetic types. It would also cause confusion to readers where the element is itself an Array. Finally, we don’t offer duplicative ways to spell the same method, and this one is already called append.
(In general, syntactic sugar has historically been the lowest priority for Swift Evolution. They also have some of the highest bars for acceptance and elicit the most bikeshedding. Probably best avoided altogether.)
Just to quickly add (though we should really start a new thread), that it also leads to ambiguity when used with array of Any. Since you don't know if you're appending a collection as element or as a list of elements. That's why append comes in two flavors; append(_:) for single element and append(contentsOf:) for list of elements.
From memory, there’s also an optimisation technique in the compiler to turn a short array literal appended with += [item] to append methods per item to avoid the array allocation altogether anyway. I’m not sure what benefit this idea has over the existing behavior.
For sure, it'd be compile-time error. The problem is that it easily leads to slow type checker, which leads to slow compilation time, IDE suggestion, etc.