aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorShinya Sato <shinnya.sato@gmail.com>2022-02-21 22:54:58 +0900
committerShinya Sato <shinnya.sato@gmail.com>2022-02-21 22:54:58 +0900
commit6d1520e44f0c804c84c9890b341a98afbed40f64 (patch)
tree0502cda0ab88eab32cfcabf3c303532472cda21a
parent2d191998c2bbd9596f5fc2029b80d48181cbfa4d (diff)
downloadinpla-6d1520e44f0c804c84c9890b341a98afbed40f64.tar.gz
inpla-6d1520e44f0c804c84c9890b341a98afbed40f64.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 5182e7a..cb48545 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 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 after 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:
+ * 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 after replacing ports of the active pair into 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)