Front page | perl.perl5.porters |
Postings from March 2018
On Tue, Mar 27, 2018 at 3:20 AM, Karl Williamson <public@khwilliamson.com> wrote: > I agree with the above. And I really don't like 'not recommended' as I > think it is too strong. Maybe just list the problems I think the main problem with the current wording is that it discourages without explaining why. In particular it doesn't explain that threads.pm does something different than what many people expect it to do. People expect it to be good for "share all the data" scenarios (because pretty much anything else called threads is), even though it is terrible at that. This confusion isn't helped by threads implementations in commonly used implementations of languages occupying the same niches as we do (e.g. cpython, Ruby MRI) sucking in exactly the opposite way (they're good at sharing but useless at actually being parallel). It's not so much threads.pm that needs a big fat warnings, it's threads::shared that does. LeonThread Previous | Thread Next