mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

(comments only) Mention unsafe TLS destructor use (#3039)

Browse Source
This commit is contained in:
Ben Blum 2012-07-26 21:04:34 -04:00
parent 3c731df890
commit 73ca5603bd
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
src/libcore/task.rs
View File

@ -945,8 +945,13 @@ fn spawn_raw(opts: task_opts, +f: fn~()) {
* task-local data slot (and use class destructors, not code inside the
* function, if specific teardown is needed). DO NOT use multiple
* instantiations of a single polymorphic function to index data of different
* types; arbitrary type coercion is possible this way. The interface is safe
* as long as all key functions are monomorphic.
* types; arbitrary type coercion is possible this way.
*
* One other exception is that this global state can be used in a destructor
* context to create a circular @-box reference, which will crash during task
* failure (see issue #3039).
*
* These two cases aside, the interface is safe.
*/
type local_data_key<T: owned> = fn@(+@T);