Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
en:toolworks:docs:apparatus:solidity [2021/08/29 22:25] – created vladius | en:toolworks:docs:apparatus:solidity [2021/10/30 12:35] (current) – vladius | ||
---|---|---|---|
Line 3: | Line 3: | ||
Apparatus implements an additional compile-time and runtime semantic which is called // | Apparatus implements an additional compile-time and runtime semantic which is called // | ||
- | The solidity state is assigned per Mechanism. | + | The solidity state is assigned per each Mechanism |
- | [[en: | + | [[en: |
you are not allowed to perform any structural changes to your Subjects and Subjectives, | you are not allowed to perform any structural changes to your Subjects and Subjectives, | ||
- | add or remove Traits, can't enable or disable Details. Spawning new Subjects and Subjectives is also prohibited. | + | add or remove Traits, can't enable or disable Details. Spawning new Subjects and Subjectives |
- | While comprising limitations | + | While comprising |
- | to Traits data (essentially eliminating the copying) and being able to operate on Subjects concurrently in a threaded manner. | + | to Traits data (essentially eliminating the copying) and being able to operate on Subjects |
- | The opposite of solidity is // | + | In its turn if you've enchained to a solid Chain you would get solid Cursors only, essentially safeguarding your Mechanic iterating/ |
+ | |||
+ | The opposite of solidity is called | ||
enchaining is active on the Mechanism, it can't be made solid and vice versa. | enchaining is active on the Mechanism, it can't be made solid and vice versa. | ||