Currently, shared tabling has many restrictions. The implementation
does not verify that the limitations are met and violating these
restrictions may cause incorrect results or crashes. Future versions are
expected to resolve these issues.
- Shared tabling currently only handles the basic scenario and cannot
yet deal with well formed semantics or incremental tabling.
- As described in section
7.9.1, abolishing shared tables may cause unnecessary waiting for
threads to complete the table.
- Only the answers of shared tables can be reclaimed, not the answer
table itself.
SWI-Prolog's continuation based tabling offers the
opportunity to perform completion using multiple threads.
