Comment 3 for bug 1809910

No problem.

Feel free to make it an even worse-case moving forward :). I was looking for something that stressed the linkage in ways that hadn't already been exposed, and that snippet was ridiculous enough that it seemed to work nicely. I'm sure we could throw some other cases in it as well.

Hopefully, the new code should be able to fix any such cases, but it doesn't hurt to explicitly put them in the "worse-case" to prevent future breakage.