I just looked over the concurrency chapter and couldn't find any mention of this.
Regards, Alex On Thu, Apr 26, 2012 at 8:51 PM, Sean Kelly <[email protected]> wrote: > On Apr 25, 2012, at 5:47 PM, Alex Rønne Petersen wrote: > > > Hi, > > > > I just noticed that std.concurrency public imports more or less all of > > the synchronization modules from druntime. This caused a whole bunch > > of name conflicts in my code. Is this really needed? The average code > > written with std.concurrency is not going to need *any* of these > > primitives - I mean, that's the entire idea. In my case, I'm doing > > very low-level hackery/abuse inside a garbage collector > > implementation, so that doesn't really count as normal usage. > > > > I know it would be a breaking change, but could we please get rid of > > those public imports? I honestly doubt anyone's relying on these, and > > they're frankly a pain in the ass. > > > > (Also, the core.thread import is private, but these are public - wat?) > > > I think it's like this because TDPL stated it works this way. I'd have to > re-read the chapter to be sure though. > _______________________________________________ > phobos mailing list > [email protected] > http://lists.puremagic.com/mailman/listinfo/phobos >
_______________________________________________ phobos mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/phobos
