infer_clone/infer/documentation/issues/STATIC_INITIALIZATION_ORDER...

This error is reported in C++. It fires when the initialization of a static
variable `A`, accesses a static variable `B` from another translation unit
(usually another `.cpp` file). There are no guarantees whether `B` has been
already initialized or not at that point.

For more technical definition and techniques to avoid/remediate, see the
[FAQ](https://isocpp.org/wiki/faq/ctors#static-init-order).
[help] scaffolding to start documenting issue types Summary: This provides some of the infrastructure needed for documentation issue types within infer itself so we can generate the website and keep it up to date when introducing new issue types. Basically each issue type has documentation in its datatype in OCaml now. But, documentation strings can be several pages of text! To avoid making IssueType.ml even more unreadable, add the option to write documentation in long form in files in infer/documentation/issues/. This implements `infer help --help-issue-type` and show-cases how documentation works for a couple of issue types. Next diff bulk-imports the current website documentation in this form. allow-large-files Reviewed By: skcho Differential Revision: D21934374 fbshipit-source-id: 2705bf424 5 years ago			`This error is reported in C++. It fires when the initialization of a static`
			variable `A`, accesses a static variable `B` from another translation unit
			(usually another `.cpp` file). There are no guarantees whether `B` has been
			`already initialized or not at that point.`

			`For more technical definition and techniques to avoid/remediate, see the`
			`[FAQ](https://isocpp.org/wiki/faq/ctors#static-init-order).`