Remove consecutive key downside

docs/syntax-structure-matching.md

@@ -320,54 +320,4 @@ local foo, bar = data.foo, data.foo.bar
 local bar = data.foo.bar
 ```
 
-This is why it is explicitly disallowed.
-
-### Consecutive key misreading
-
-Consider this syntax.
-
-```Lua
-{ foo, bar, baz }
-```
-
-This desugars to:
-
-```Lua
-{ [1] = foo, [2] = bar, [3] = baz }
-```
-
-But an untrained observer may interpret it as:
-
-```Lua
-{ .foo = foo, .bar = bar, .baz = baz }
-```
-
-Of course, we have rigorously defined dot keys without names to allow for this use case:
-
-```Lua
-{ .foo, .bar, .baz }
-```
-
-But, while it fits into the desugaring logic, it is an open question whether we feel this is sufficient distinction.
-
-One case in favour of this proposal is that Luau already uses similar syntax for array literals:
-
-```Lua
-local myArray = { foo, bar, baz }
-```
-
-But one case against is that JavaScript uses brackets/braces to dinstinguish arrays and maps, and a Luau array looks like a JS map:
-
-```JS
-let { foo, bar, baz } = data;
-```
-
-Whether this downside is actually significant enough should be discussed in comments though.
-
-Consecutive keys are arguably most useful when used with tuple-like types like `{1, "foo", true}`, as they can match each value by position:
-
-```Luau
-{ id, text, isNeat }
-```
-
-However, Luau does not allow these types to be expressed at the moment. It isn't out of the question that we could support this in the future, so the door should likely be left open for tuple-like tables.
+This is why it is explicitly disallowed.