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.

Jeremy Dubreil 878add3fad [eradicate] no longer report Field Not Nullable warnings on the Fragment onDestroy method ... Summary: It is common on Android code to recycle the `View` object by nullifying them in the `onDestroy()` or `onDestroyView()` methods. In this case, the outer `Fragment` object structure is preserve while the inner `View` object are set to null for the garbage collect to release the memory. However, if the fields are only set to `null` in the `onDestroy*()` methods, those fields cannot be `null` during the active lifecycle of the `Fragment`, so it is not necessary to annotate those fields with `Nullable`. Reviewed By: mbouaziz Differential Revision: D10024458 fbshipit-source-id: b05e538d9		6 years ago
..
annotations	[starvation] add NonBlocking annotation	7 years ago
bin	[make] make infer/src/Makefile less phony	8 years ago
etc	[clang] replace yojson frontend with biniou frontend	9 years ago
lib	[infer][buck] use a unique name for the Infer Javac wrapper	6 years ago
man/man1	changes missed in commit "[starvation] refactor method matching ; kill dev-android-strict-mode option"	6 years ago
models	[infer][PR] Fix getcwd model to allow NULL argument	6 years ago
src	[eradicate] no longer report Field Not Nullable warnings on the Fragment onDestroy method	6 years ago
tests	[eradicate] no longer report Field Not Nullable warnings on the Fragment onDestroy method	6 years ago
.ocp-indent	add ocp-indent configuration and eclipse launcher	9 years ago