[website] make doc-publish

Summary: Updating the website with latest doc changes.

Reviewed By: skcho

Differential Revision: D53663484

fbshipit-source-id: 5c19944d72f783a3f090c04ca0be83cde427cb30

website/docs/all-issue-types.md

@@ -527,6 +527,30 @@ Create an intent/start a component using a (possibly user-controlled) URI. may o
 Reported as "Cross Site Scripting" by [quandary](/docs/next/checker-quandary).
 
 Untrusted data flows into HTML; XSS risk.
+## CXX_REF_CAPTURED_IN_BLOCK
+
+Reported as "C++ Reference Captured in Block" by [self-in-block](/docs/next/checker-self-in-block).
+
+This check flags when a C++ reference is captured in an escaping block.
+This means that the block will be leaving the current scope, i.e. it is
+not annotated with `__attribute__((noescape))`.
+
+Example:
+
+```
+- (void)ref_captured_in_escaping_block_bad:(int&)y {
+  dispatch_async(dispatch_get_main_queue(), ^{
+    int a = y;
+    ...
+  });
+  ...;
+}
+```
+
+This could cause crashes because C++ references are not managed pointers
+(like ARC pointers) and so the referent is likely to be gone if the block
+dereferences it later.
+
 ## DANGLING_POINTER_DEREFERENCE
 
 Reported as "Dangling Pointer Dereference" by [biabduction](/docs/next/checker-biabduction).

website/docs/checker-self-in-block.md

@@ -21,6 +21,7 @@ Supported languages:
 
 The following issue types are reported by this checker:
 - [CAPTURED_STRONG_SELF](/docs/next/all-issue-types#captured_strong_self)
+- [CXX_REF_CAPTURED_IN_BLOCK](/docs/next/all-issue-types#cxx_ref_captured_in_block)
 - [MIXED_SELF_WEAKSELF](/docs/next/all-issue-types#mixed_self_weakself)
 - [MULTIPLE_WEAKSELF](/docs/next/all-issue-types#multiple_weakself)
 - [STRONG_SELF_NOT_CHECKED](/docs/next/all-issue-types#strong_self_not_checked)