Generate Javadoc and JDiff for Guava 999.0.0-HEAD-jre-SNAPSHOT

Author: copybara-service[bot]

releases/snapshot-android/api/diffs/snapshot-android.xml

@@ -5717,6 +5717,8 @@
  iterable, but when using this option, it can (if the input sequence consists of nothing but
  separators).
 
+ <p>If a limit is also specified, see {@link #limit} for how the two options interact.
+
  @return a splitter with the desired configuration]]>
       </doc>
     </method>
@@ -5737,6 +5739,13 @@
  trimmed, including the last. Hence {@code Splitter.on(',').limit(3).trimResults().split(" a , b
  , c , d ")} results in {@code ["a", "b", "c , d"]}.
 
+ <p>Note that when empty strings are omitted, they do not count even in determining where the
+ final element begins. The final element starts with the first piece that is not omitted, so
+ separators that delimit omitted empty strings do not appear in it, even though later separators
+ do. For example, {@code Splitter.on(',').limit(2).omitEmptyStrings().split("a,,b,c")} returns
+ an iterable containing {@code ["a", "b,c"]}, not {@code ["a", ",b,c"]}: the second comma
+ delimits an empty string, so it is not part of the final element.
+
  @param maxItems the maximum number of items returned
  @return a splitter with the desired configuration
  @since 9.0]]>

releases/snapshot-android/api/docs/com/google/common/base/Splitter.html

@@ -449,7 +449,9 @@ <h3>omitEmptyStrings</h3>
 
 <p>Note that it is ordinarily not possible for <a href="#split(java.lang.CharSequence)"><code>split(CharSequence)</code></a> to return an empty
 iterable, but when using this option, it can (if the input sequence consists of nothing but
-separators).</div>
+separators).
+
+<p>If a limit is also specified, see <code>limit</code> for how the two options interact.</div>
 <dl class="notes">
 <dt>Returns:</dt>
 <dd>a splitter with the desired configuration</dd>
@@ -471,7 +473,14 @@ <h3>limit</h3>
 count. Hence, <code>Splitter.on(',').limit(3).omitEmptyStrings().split("a,,,b,,,c,d")</code> returns
 an iterable containing <code>["a", "b", "c,d"]</code>. When trim is requested, all entries are
 trimmed, including the last. Hence <code>Splitter.on(',').limit(3).trimResults().split(" a , b
-, c , d ")</code> results in <code>["a", "b", "c , d"]</code>.</div>
+, c , d ")</code> results in <code>["a", "b", "c , d"]</code>.
+
+<p>Note that when empty strings are omitted, they do not count even in determining where the
+final element begins. The final element starts with the first piece that is not omitted, so
+separators that delimit omitted empty strings do not appear in it, even though later separators
+do. For example, <code>Splitter.on(',').limit(2).omitEmptyStrings().split("a,,b,c")</code> returns
+an iterable containing <code>["a", "b,c"]</code>, not <code>["a", ",b,c"]</code>: the second comma
+delimits an empty string, so it is not part of the final element.</div>
 <dl class="notes">
 <dt>Parameters:</dt>
 <dd><code>maxItems</code> - the maximum number of items returned</dd>

releases/snapshot-jre/api/diffs/snapshot-jre.xml

@@ -5730,6 +5730,8 @@
  iterable, but when using this option, it can (if the input sequence consists of nothing but
  separators).
 
+ <p>If a limit is also specified, see {@link #limit} for how the two options interact.
+
  @return a splitter with the desired configuration]]>
       </doc>
     </method>
@@ -5750,6 +5752,13 @@
  trimmed, including the last. Hence {@code Splitter.on(',').limit(3).trimResults().split(" a , b
  , c , d ")} results in {@code ["a", "b", "c , d"]}.
 
+ <p>Note that when empty strings are omitted, they do not count even in determining where the
+ final element begins. The final element starts with the first piece that is not omitted, so
+ separators that delimit omitted empty strings do not appear in it, even though later separators
+ do. For example, {@code Splitter.on(',').limit(2).omitEmptyStrings().split("a,,b,c")} returns
+ an iterable containing {@code ["a", "b,c"]}, not {@code ["a", ",b,c"]}: the second comma
+ delimits an empty string, so it is not part of the final element.
+
  @param maxItems the maximum number of items returned
  @return a splitter with the desired configuration
  @since 9.0]]>

releases/snapshot-jre/api/docs/com/google/common/base/Splitter.html

@@ -449,7 +449,9 @@ <h3>omitEmptyStrings</h3>
 
 <p>Note that it is ordinarily not possible for <a href="#split(java.lang.CharSequence)"><code>split(CharSequence)</code></a> to return an empty
 iterable, but when using this option, it can (if the input sequence consists of nothing but
-separators).</div>
+separators).
+
+<p>If a limit is also specified, see <code>limit</code> for how the two options interact.</div>
 <dl class="notes">
 <dt>Returns:</dt>
 <dd>a splitter with the desired configuration</dd>
@@ -471,7 +473,14 @@ <h3>limit</h3>
 count. Hence, <code>Splitter.on(',').limit(3).omitEmptyStrings().split("a,,,b,,,c,d")</code> returns
 an iterable containing <code>["a", "b", "c,d"]</code>. When trim is requested, all entries are
 trimmed, including the last. Hence <code>Splitter.on(',').limit(3).trimResults().split(" a , b
-, c , d ")</code> results in <code>["a", "b", "c , d"]</code>.</div>
+, c , d ")</code> results in <code>["a", "b", "c , d"]</code>.
+
+<p>Note that when empty strings are omitted, they do not count even in determining where the
+final element begins. The final element starts with the first piece that is not omitted, so
+separators that delimit omitted empty strings do not appear in it, even though later separators
+do. For example, <code>Splitter.on(',').limit(2).omitEmptyStrings().split("a,,b,c")</code> returns
+an iterable containing <code>["a", "b,c"]</code>, not <code>["a", ",b,c"]</code>: the second comma
+delimits an empty string, so it is not part of the final element.</div>
 <dl class="notes">
 <dt>Parameters:</dt>
 <dd><code>maxItems</code> - the maximum number of items returned</dd>