| … | … | @@ -57,9 +57,19 @@ be redesigned as described below. |
| 57 | 57 | |
| 58 | 58 | Since the initial idea of `PureExec` was purity, it could not be used |
| 59 | 59 | for tail-recursive, serialized execution in the current AtomSpace: so an |
| 60 | | argument is added: which AtomSpace the execution |
| 60 | argument is added: which AtomSpace the execution. The proposal here is |
| 61 | to generalize this to allow a GPU to be specified, or more generally an |
| 62 | external object. |
| 63 | |
| 64 | But first, a distraction: |
| 65 | The `ExecutThreadedLink` gathers results into a QueueValue. There needs |
| 66 | to be a `NullLink` which says "execute me but discard the return value". |
| 67 | But such a `NullLink` could naturally do serial execution. So ... it |
| 68 | suggests that we need a "serial exec and gather the return values" as |
| 69 | well as a "serial exec and discard the return values" link types. What |
| 70 | names should they be given? |
| 61 | 71 | |
| 62 | 72 | TODO List |
| 63 | 73 | --------- |
| 64 | 74 | Writiing the above, the TODO list expands: |
| 65 | | * |
| 75 | * The ThreadJoinLink should be removed from Atomese. |