Disable trigger rule, since it's not compatible with negation delay.

Temporarily disable MC_E too.

Author: sei-eschwartz

share/prolog/oorules/rules.pl

@@ -2253,13 +2253,14 @@
 % information about the direction of that relationship.
 :- table reasonClassRelatedMethod/2 as incremental.
 :- table reasonClassRelatedMethod_A/2 as incremental.
-%:- table reasonClassRelatedMethod_B/2 as incremental.
+:- table reasonClassRelatedMethod_B/2 as incremental.
 :- table reasonClassRelatedMethod_C/2 as incremental.
 
 reasonClassRelatedMethod(Class, Method) :-
     reasonClassRelatedMethod_A(Class, Method);
     % _B is now a trigger rule
-    %reasonClassRelatedMethod_B(Class, Method);
+    % Re-enabled (temporarily) for negation branch
+    reasonClassRelatedMethod_B(Class, Method);
     reasonClassRelatedMethod_C(Class, Method).
 
 % ClassCallsMethod => ClassRelatedMethod
@@ -2270,6 +2271,9 @@
 thisPtrUsage(Function, ThisPtr, Method) :-
     thisPtrUsage(_, Function, ThisPtr, Method).
 
+reasonClassRelatedMethod_B(Class1, Method2) :-
+    reasonClassRelatedMethod_B(Class1, _, _, Method2).
+
 % Because two methods are called on the same this-pointer in the same function.  This rule is
 % NOT direction safe, because it simply observes two methods being called on the same object
 % pointer, and does not account for inheritance relationships.
@@ -2695,6 +2699,7 @@
 % inverse rule under reasonNOTMergeClasses.
 % PAPER: Merging-4
 reasonMergeClasses_E(Class1, Class2) :-
+    fail,
     factDerivedClass(DerivedClass, Class1, ObjectOffset),
     factDerivedClass(DerivedClass, Class2, ObjectOffset),
     iso_dif(Class1, Class2),