Merge branch 'master' into master

Author: axgillies

_includes/side-nav-fast.html

@@ -1,7 +1,8 @@
 <ul class="doc-side-nav">
    <li><h5 class="doc-side-nav-title">
-    <a href="{{ site.baseurl }}/fast/">Fast Tips</a></h5>
+    <a href="{{ site.baseurl }}/fast/">Performance Guide</a></h5>
    </li>
+   <li><h6 class="doc-side-nav-title">Fast Tips</h6></li>
    {% assign sorted_posts = site.posts | sort: 'order' %}
 
    {% for post in sorted_posts %}

_includes/sticky-nav.html

@@ -20,7 +20,7 @@
           <li><a href="{{ site.baseurl }}/about" {% if current[1] == 'about' %}class='current'{% endif %}>About</a></li>
           <li><a href="{{ site.baseurl }}/docs/cpp" {% if current[1] == 'cpp.html' %}class='current'{% endif %}>C++ Guide</a></li>
           <li><a href="{{ site.baseurl }}/tips/" {% if current[1] == 'tips' %}class='current'{% endif %}>C++ Tips</a></li>
-          <li><a href="{{ site.baseurl }}/fast/" {% if current[1] == 'fast' %}class='current'{% endif %}Fast Tips</a></li>
+          <li><a href="{{ site.baseurl }}/fast/" {% if current[1] == 'fast' %}class='current'{% endif %}>Fast Tips</a></li>
           <li><a href="{{ site.baseurl }}/docs/python" {% if current[1] == 'python.html' %}class='current'{% endif %}>Python Guide</a></li>
           <li><a href="{{ site.baseurl }}/blog/" {% if current[1] == 'blog' %}class='current'{% endif %}>Blog</a></li>
           <li><a href="{{ site.baseurl }}/community/" {% if current[1] == 'community' %}class='current'{% endif %}>Community</a></li>

_layouts/blog.html

@@ -20,7 +20,7 @@ <h1>{{page.title}}</h1>
     title="Subscribe to Abseil Blog &amp; Tips"
     rel="alternate"
     type="application/rss+xml">
-    <img src="//feedburner.google.com/fb/images/pub/feed-icon32x32.png"
+    <img src="//gstatic.com/ac/dashboard/feedburner-32.png"
          alt="Subscribe to the Abseil Blog" style="border:0;">
     </img>
 </a>

_layouts/fast.html

@@ -21,7 +21,7 @@ <h1>{{page.title}}</h1>
     title="Subscribe to Abseil Blog &amp; Tips"
     rel="alternate"
     type="application/rss+xml">
-    <img src="//feedburner.google.com/fb/images/pub/feed-icon32x32.png"
+    <img src="//gstatic.com/ac/dashboard/feedburner-32.png"
          alt="Subscribe to the Abseil Blog" style="border:0;">
     </img>
 </a>

_layouts/tips.html

@@ -21,7 +21,7 @@ <h1>{{page.title}}</h1>
     title="Subscribe to Abseil Blog &amp; Tips"
     rel="alternate"
     type="application/rss+xml">
-    <img src="//feedburner.google.com/fb/images/pub/feed-icon32x32.png"
+    <img src="//gstatic.com/ac/dashboard/feedburner-32.png"
          alt="Subscribe to the Abseil Blog" style="border:0;">
     </img>
 </a>

_posts/2017-09-26-totw-1.md

@@ -90,9 +90,19 @@ void AlreadyHasCharStar(const char* s) {
 
 Because the `string_view` does not own its data, any strings pointed to by the
 `string_view` (just like a `const char*`) must have a known lifespan, and must
-outlast the `string_view` itself. This means that using `string_view` for
-storage is often questionable: you need some proof that the underlying data will
-outlive the `string_view`.
+outlast the `string_view` itself.
+
+This means that using `string_view` for storage is often questionable: you need
+some proof that the underlying data will outlive the `string_view`. For example,
+the following struct probably doesn't make sense if it might be stored beyond
+the result of a function call that accepts it as a parameter:
+
+<pre class="prettyprint lang-cpp bad-code">
+struct TestScore {
+  absl::string_view username;  // Probably should be a `std::string`
+  double score;
+};
+</pre>
 
 If your API only needs to reference the string data during a single call, and
 doesn't need to modify the data, accepting a `string_view` is sufficient.

_posts/2018-02-15-totw-88.md

@@ -104,7 +104,7 @@ variable?", both to follow in your own code and to cite in your code reviews:
   ```cpp
   // Bad code
 
-  // Could invoke an intializer list constructor, or a two-argument constructor.
+  // Could invoke an initializer list constructor, or a two-argument constructor.
   Frobber frobber{size, &bazzer_to_duplicate};
 
   // Makes a vector of two doubles.

_posts/2018-02-22-totw-93.md

@@ -42,8 +42,8 @@ Some of the benefits of using `Span` as a function parameter are similar to
 those of using `string_view`.
 
 The caller can pass a slice of the original vector, or pass a plain array. It is
-also compatible with other array-like containers, like `InlinedVector`,
-`FixedArray`, `google::protobuf::RepeatedField`, etc.
+also compatible with other array-like containers, like `absl::InlinedVector`,
+`absl::FixedArray`, `google::protobuf::RepeatedField`, etc.
 
 As with `string_view`, it is usually better to pass `Span` by value when used as
 a function parameter - this form is slightly faster, and produces smaller code.

_posts/2018-05-03-totw-148.md

@@ -10,7 +10,7 @@ order: "148"
 
 Originally posted as TotW #148 on May 3, 2018
 
-*By [Titus Winters](mailto:titus@google.com)*
+*By [Titus Winters](mailto:titus@cs.ucr.edu)*
 
 Updated 2020-04-06
 

_posts/2018-05-03-totw-149.md

@@ -10,7 +10,7 @@ order: "149"
 
 Originally posted as TotW #149 on May 3, 2018
 
-*By [Titus Winters](mailto:titus@google.com)*
+*By [Titus Winters](mailto:titus@cs.ucr.edu)*
 
 Updated 2020-04-06
 
@@ -188,8 +188,8 @@ expressed in those types, not in the APIs that operate on them.
 ### Ref-qualification
 
 As a side note: it's possible to apply the same reasoning for ref-qualifiers on
-destructive accessors. Consider a class like `std::stringbuf` - in C++20 it will
-gain an accessor to consume the contained string, presented as an overload set
+destructive accessors. Consider a class like `std::stringbuf` - in C++20 it
+gained an accessor to consume the contained string, presented as an overload set
 with the existing accessor:
 
 <pre class="prettyprint lang-cpp code">