aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorShinya Sato <shinnya.sato@gmail.com>2022-02-21 22:43:08 +0900
committerShinya Sato <shinnya.sato@gmail.com>2022-02-21 22:43:08 +0900
commit2d1a84fa00980658a0495c075f6db14ed09ba0f0 (patch)
treed51ccda69bcb3fdc199739dbbc4bd6186c9ff4f8
parent40554711b8909c2e5102c72adfb8c052b0636679 (diff)
downloadinpla-2d1a84fa00980658a0495c075f6db14ed09ba0f0.tar.gz
inpla-2d1a84fa00980658a0495c075f6db14ed09ba0f0.zip
Update Changelog.md
-rw-r--r--Changelog.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/Changelog.md b/Changelog.md
index 7a8fc46..fd95ae1 100644
--- a/Changelog.md
+++ b/Changelog.md
@@ -5,7 +5,7 @@
#### Polished:
* **Bytecode optimisation inspired by Tail Recursive Optimisation**: As a result, this optimisation brings about faster computation up to about twice in comparison with no reuse-annotated computation.
- * When an interaction rule has a connection whose the left and the right hand sides have the same IDs to the active pair, computation of the connection can be realised by applying the same bytecode sequence of the rule to the connection with replacing ports of active pairs into the agent ports of the connection. Moreover, when the connection is placed at the tail of connection sequences, we can restart the same bytecode sequence after replacing these ports. For instance, take the following rule for Fibonacci number:
+ * When an interaction rule has a connection whose both sides agents have the same IDs to the active pair, computation of the connection can be realised by applying the same bytecode sequence of the rule to the connection with replacing ports of active pairs into the agent ports of the connection. Moreover, when the connection is placed at the tail of a connection sequence, we can restart the same bytecode sequence after replacing these ports. For instance, take the following rule for Fibonacci number:
```
fib(ret) >< (int n)