[pypy-commit] pypy default: STM future work: add a couple of sentences.

[arigo]

Author: Armin Rigo <arigo at tunes.org>
Branch: 
Changeset: r57636:6f82f37eb244
Date: 2012-09-28 12:37 +0200
http://bitbucket.org/pypy/pypy/changeset/6f82f37eb244/

Log:	STM future work: add a couple of sentences.

diff --git a/pypy/doc/project-ideas.rst b/pypy/doc/project-ideas.rst
--- a/pypy/doc/project-ideas.rst
+++ b/pypy/doc/project-ideas.rst
@@ -115,13 +115,16 @@
   which data structures would be more appropriate?  For example, a dict
   implemented as a hash table will suffer "stm collisions" in all threads
   whenever one thread writes anything to it; but there could be other
-  implementations.
+  implementations.  Maybe alternate strategies can be implemented at the
+  level of the Python interpreter (see list/dict strategies,
+  ``pypy/objspace/std/{list,dict}object.py``).
 
 * More generally, there is the idea that we would need some kind of
   "debugger"-like tool to "debug" things that are not bugs, but stm
   conflicts.  How would this tool look like to the end Python
   programmers?  Like a profiler?  Or like a debugger with breakpoints
-  on aborted transactions?
+  on aborted transactions?  It would probably be all app-level, with
+  a few hooks e.g. for transaction conflicts.
 
 * Find good ways to have libraries using internally threads and atomics,
   but not exposing threads to the user.  Right now there is a rough draft