You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently all locks in Chasm are "deep lock".
However, in most cases, shallow locks would be preferred.
Imagine targeting a single instruction in a method. If a transformation applies a write lock to said instruction, all other transformations are not allow to change anything about it.
However, in most cases the intended behavior will be that noone modifies the location of said instruction. Shallow locks provide that option, allowing other transformations to modify childrens of the target, but not the target itself.
The text was updated successfully, but these errors were encountered:
Currently all locks in Chasm are "deep lock".
However, in most cases, shallow locks would be preferred.
Imagine targeting a single instruction in a method. If a transformation applies a write lock to said instruction, all other transformations are not allow to change anything about it.
However, in most cases the intended behavior will be that noone modifies the location of said instruction. Shallow locks provide that option, allowing other transformations to modify childrens of the target, but not the target itself.
The text was updated successfully, but these errors were encountered: