Difference between revisions of "Concurrency planning"
From IokeWiki
| Line 1: | Line 1: | ||
| − | |||
=== My ([[User:olabini|Ola Bini]]) current thoughts on concurrency === | === My ([[User:olabini|Ola Bini]]) current thoughts on concurrency === | ||
| Line 6: | Line 5: | ||
a future implemented in terms of aspects: | a future implemented in terms of aspects: | ||
| − | + | <source lang="ioke"> | |
Future before(:any, except: [:become, :forceResult], | Future before(:any, except: [:become, :forceResult], | ||
self become(self forceResult)) | self become(self forceResult)) | ||
| − | + | </source> | |
Latest revision as of 15:36, 24 November 2010
My (Ola Bini) current thoughts on concurrency
futures with agents, like Io, agents are a thread pool, futures become the real value when needed. agents can be spun off too. use some other syntax since @ is taken. lazy operator is a lexical kinda thing that just does the operations inside it when it's needed. a future implemented in terms of aspects:
Future before(:any, except: [:become, :forceResult],
self become(self forceResult))
