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
Fault effects might potentially use a wrong member when the member is new'ed by a fault effect that is higher in the transformed type hierarchy. The underlying reason is that the original code binds the fault effect to the original member (because the new'ed one is not in scope as there is no inheritance relation), but the transformed code binds to the new'ed member as the new'ed one is closer once the inheritance hierarchy implementing the fault effects is formed.
Possible resolutions:
(Easy solution) Forbid such (very unlikely) situations with the help of an analyzer.
(Hard solution) Transform the code so that the correct member is used; might not be generally possible in all situations.
The text was updated successfully, but these errors were encountered:
Fault effects might potentially use a wrong member when the member is
new
'ed by a fault effect that is higher in the transformed type hierarchy. The underlying reason is that the original code binds the fault effect to the original member (because thenew
'ed one is not in scope as there is no inheritance relation), but the transformed code binds to thenew
'ed member as thenew
'ed one is closer once the inheritance hierarchy implementing the fault effects is formed.Possible resolutions:
The text was updated successfully, but these errors were encountered: