[D-runtime] Why do we expose thread_init()?
Sean Kelly
sean at invisibleduck.org
Thu Jun 21 22:37:35 PDT 2012
On Jun 21, 2012, at 9:46 AM, Alex Rønne Petersen wrote:
> Hi,
>
> Is there any particular reason we expose thread_init() in core.thread?
> This seems like the kind of function that really shouldn't be in the
> public API since it's used for internal runtime initialization.
Most of the extern © calls are not really meant for public use. thread_init() has this name mostly because the namespace chosen for thread stuff was "thread_". It would be easy enough to mark it private though.
More information about the D-runtime
mailing list