I've seen this sentiment from a number of folks, that we should "wait and see" whether we need the syntactic sugar and add it later.
I don't think that approach is a good one for the Swift community. If the end state is that we will have type sugar for InlineArray, then the community benefits from have that type sugar introduced at the same time as InlineArray. That way, all of the documentation, tutorials, talks, style guides, examples, and so on can take the type sugar into account. Developers can learn its meaning once and use it going forward. There's a cost to making changes later on, even if it's as simple as adding new sugar, because you've invalidated some of the existing body of knowledge.
We shouldn't delay the introduction of type sugar just because we're afraid to make a decision now. This is a highly-requested feature, and has been for years: it's going to get used. The uses we envision today aren't going to be largely different from the uses tomorrow.
Let's find the best solution for this type sugar---or no solution, if this problem isn't big enough to solve---so we can introduce and teach it once.
Doug