> > Since Python has nothing really private, this implies in
> > fact to protect every single object for free threading,
> > although nobody wants this in the first place to happen.
>
> How does Java solve this problem? (Is this analagous to native vs. green
> threads?)
>
> > Python is not designed for that. Why do you want to enforce
> > the impossible, letting every object pay a high penalty
> > to become completely thread-safe?
>
> Hmm, how about declaring only certain builtins as free-thread safe? Or is
> "the impossible" necessary because of the nature of incref/decref?
http://www.javacats.com/US/articles/MultiThreading.html
I would like
sync foo:
bloc of code here
maybe we could merge in some Occam while were at it. B^)
sync would be a most excellent operator in python.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4