You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Jules Villard f411c7d131 [pulse] do not stop at the first error in function calls ... Summary: We deliberately stopped as soon as an error was detected when applying a function call. This is not good as other pre/posts of the function may apply cleanly, which would allow us to cover more behaviours of the code. Went on a bit of a refactoring tangeant while fixing this, to clarify the `Ok None`/`Ok Some _`/`Error _` datatype returned by PulseInterproc. Now we report errors as soon as we find them during function calls but continue accumulating specs afterwards. Reviewed By: da319 Differential Revision: D24888768 fbshipit-source-id: d5f2c29d7		4 years ago
..
c	[clang] fix bad interaction between ConditionalOperator and initializers	4 years ago
cpp	[pulse] do not stop at the first error in function calls	4 years ago
java	[starvation] acquisitions mod location	4 years ago
objc	[clang] fix bad interaction between ConditionalOperator and initializers	4 years ago
objcpp	[closures preanalysis] [3/n] Adding models to dispatch functions and remove code for previous specialization and dispatch models	4 years ago