Which order to run box annihilator and TLS dtor?

[brson]

It looks like in the current codebase we need to run the annihilator before the TLS dtor because rustc has boxes in cycles that access TLS, but TLS dtors could also create cycles requiring GC. Not sure how to resolve this interdependency.

[brson]

Actually, not sure what's going on here. It's late. Need sleep.

[brson]

This is exposed in a few compile-fail tests including infinite-instantiation.

[bblum]

Is the LocalStorage version of TLS not used exclusively by the stdlib? If it is, we could just rtabort if a TLS destructor tries to use @-pointers.

Definitely related to #6996. There may be no way around it no matter which runtime is plugged in. It strikes me as "just as bad" as failing from a destructor while unwinding.

[brson]

LocalStorage is just the type used to hold the opaque pointer used by the TLS implementation. It holds the map of all the task local values, including arbitrary destructors.

[alexcrichton]

Note that this is likely also concerned modifying TLS when destroying TLS, or possibly creating @ when destroying @

[pnkfelix]

cc me

[thestinger]

Gc has been removed so this is no longer relevant.