Comment 3 for bug 1811044

I'm sure there are other options as well. To fix the bug we could do a combination. Start with the the simple fix that could be backported so people who _have_ already removed it and may not have updated versioning on these old containers, everything still works. and the second can be the actual deprecation, which we could include in the next swift release?

Obviously, in any case, I'll like to also come up with a test to try and demonstrate this bug. Probe test? Anyway, that's a future Matt problem :P