View source code Display the source code in core/thread.d from which this page was generated on github. Improve this page Quickly fork, edit online, and submit a pull request for this page. Requires a signed-in GitHub account. This works well for small changes. If you'd like to make larger changes you may want to consider using local clone. Page wiki View or edit the community-maintained wiki page associated with this page.

Function core.thread.thread_enterCriticalRegion

Signals that the code following this call is a critical region. Any code in this region must finish running before the calling thread can be suspended by a call to thread_suspendAll.

This function is, in particular, meant to help maintain garbage collector invariants when a lock is not used.

A critical region is exited with thread_exitCriticalRegion.

Warning: Using critical regions is extremely error-prone. For instance, using locks inside a critical region can easily result in a deadlock when another thread holding the lock already got suspended.

The term and concept of a 'critical region' comes from .

Prototype

extern(C) void thread_enterCriticalRegion();

In

The calling thread must be attached to the runtime.

Authors

Sean Kelly, Walter Bright, Alex Rønne Petersen, Martin Nowak

License

Distributed under the Boost Software License 1.0. (See accompanying file LICENSE)

Comments