en:toolworks:docs:apparatus:solidity

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
en:toolworks:docs:apparatus:solidity [2021/08/29 22:25] – created vladiusen: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 //solidity// (or being //solid//). Apparatus implements an additional compile-time and runtime semantic which is called //solidity// (or being //solid//).
  
-The solidity state is assigned per Mechanism. It is managed automatically, during the +The solidity state is assigned per each Mechanism of the Machine individuallyThis is managed automatically, during the 
-[[en:toolworks:docs:apparatus:enchaining|enchaining]]. When the Mechanism is in a solid state,+[[en:toolworks:docs:apparatus:enchaining|enchaining]] operation. When the Mechanism is in a solid state,
 you are not allowed to perform any structural changes to your Subjects and Subjectives, i.e. you can't you are not allowed to perform any structural changes to your Subjects and Subjectives, i.e. you can't
-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 within a solid Mechanism is also prohibited.
  
-While comprising limitations such homogeneous state provides for some very important features like direct memory access +While comprising aforementioned limitations this uniform state provides for some very important features like direct memory access 
-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 and Subjectives concurrently in a threaded manner.
  
-The opposite of solidity is //liquidity// (or being //liquid//) which is the default behavior. If the liquid (non-solid)+In its turn if you've enchained to a solid Chain you would get solid Cursors only, essentially safeguarding your Mechanic iterating/operating. 
 + 
 +The opposite of solidity is called //liquidity// (or being //liquid//) which is the default behavior. If the liquid (non-solid)
 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.
  
  • en/toolworks/docs/apparatus/solidity.1630265137.txt.gz
  • Last modified: 2021/08/29 22:25
  • by vladius