diff options
| author | Shinya Sato <shinnya.sato@gmail.com> | 2022-02-21 22:54:58 +0900 |
|---|---|---|
| committer | Shinya Sato <shinnya.sato@gmail.com> | 2022-02-21 22:54:58 +0900 |
| commit | 6d1520e44f0c804c84c9890b341a98afbed40f64 (patch) | |
| tree | 0502cda0ab88eab32cfcabf3c303532472cda21a /Changelog.md | |
| parent | 2d191998c2bbd9596f5fc2029b80d48181cbfa4d (diff) | |
| download | inpla-6d1520e44f0c804c84c9890b341a98afbed40f64.tar.gz inpla-6d1520e44f0c804c84c9890b341a98afbed40f64.zip | |
Update Changelog.md
Diffstat (limited to 'Changelog.md')
| -rw-r--r-- | Changelog.md | 2 |
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) |
