| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2014-12-05 | prefer "FIXME" to "TODO". | Aidan Cully | -1/+1 | |
| 2014-12-05 | work around portability issue on FreeBSD, in which the key returned from | Aidan Cully | -1/+17 | |
| pthread_key_create can be 0. | ||||
| 2014-11-24 | std: Leak all statically allocated TLS keys | Alex Crichton | -35/+2 | |
| It turns out that rustrt::at_exit() doesn't actually occur after all pthread threads have exited (nor does atexit()), so there's not actually a known point at which we can deallocate these keys. It's not super critical that we do so, however, because we're about to exit anyway! Closes #19280 | ||||
| 2014-11-23 | std: Add a new top-level thread_local module | Alex Crichton | -0/+306 | |
| This commit removes the `std::local_data` module in favor of a new `std::thread_local` module providing thread local storage. The module provides two variants of TLS: one which owns its contents and one which is based on scoped references. Each implementation has pros and cons listed in the documentation. Both flavors have accessors through a function called `with` which yield a reference to a closure provided. Both flavors also panic if a reference cannot be yielded and provide a function to test whether an access would panic or not. This is an implementation of [RFC 461][rfc] and full details can be found in that RFC. This is a breaking change due to the removal of the `std::local_data` module. All users can migrate to the new thread local system like so: thread_local!(static FOO: Rc<RefCell<Option<T>>> = Rc::new(RefCell::new(None))) The old `local_data` module inherently contained the `Rc<RefCell<Option<T>>>` as an implementation detail which must now be explicitly stated by users. [rfc]: https://github.com/rust-lang/rfcs/pull/461 [breaking-change] | ||||
