3 Commits (2e01d3402f8eb7f3d3cf6510e7e03ea61e9a9a6f)

Author	SHA1	Message	Date
jrm	0cd533f892	Enforcing subtyping rules for @Expensive and @PerformanceCritical ... Summary: public This adds the following subtyping rules: - methods that are not annotated with Expensive cannot be overwritten by a method annotated with Expensive - methods annotated with PerformanceCritical must be overwitten by method annotated with PerformanceCritical Reviewed By: cristianoc Differential Revision: D2636076 fb-gh-sync-id: eb616c9	9 years ago
jrm	6b6b4d1949	Detecting if methods annotated with @PerformanceCritical transitively call methods annotated with @Expensive ... Summary: public Just works by running the analysis bottom-up and promoting any method as virtually annotated with `Expensive` whenever one of its callee is annotated with `Expensive` Reviewed By: cristianoc Differential Revision: D2635242 fb-gh-sync-id: 4401be6	9 years ago
jrm	f5ddb983fe	Initial version of the @Expensive checker ... Summary: public This is an initial version of the Expensive checker which only report violations on direct calls. The main objective is to setup all the files for this new checker. The next steps are: 1) run the checker in interprocedural mode 2) Save in the summary of a method foo() the annotation attribute Expensive if a direct callee of foo is annotated with Expensive 3) Check that Expensive is enforced by subtyping, i.e. check that non-expensive method cannot be overwritten by a method annotated with Expensive Reviewed By: cristianoc Differential Revision: D2629947 fb-gh-sync-id: 0e06f85	9 years ago