CheckedFuture cannot properly support the chained operations that are the
primary goal of ListenableFuture. CheckedFuture also encourages users to
rethrow exceptions from one thread in another thread, producing misleading stack traces.
Additionally, it has a surprising policy about which exceptions to map and which to leave
untouched. Guava users who want a CheckedFuture can fork the classes for their own
use, possibly specializing them to the particular exception type they use. We recommend that
most people use ListenableFuture and perform any exception wrapping themselves. This
class is scheduled for removal from Guava in February 2018.

The "base64url" encoding specified by
RFC 4648 section 5, Base 64 Encoding
with URL and Filename Safe Alphabet, also sometimes referred to as the "web safe Base64." (This
is the same as the base 64 encoding with URL and filename safe alphabet from
RFC 3548.)

A builder of LoadingCache and Cache instances having any combination of the
following features:
automatic loading of entries into the cache
least-recently-used eviction when a maximum size is exceeded
time-based expiration of entries, measured since last access or last write
keys automatically wrapped in weak references
values automatically wrapped in weak or soft references
notification of evicted (or otherwise removed) entries
accumulation of cache access statistics

CheckedFuture cannot properly support the chained operations that are the
primary goal of ListenableFuture. CheckedFuture also encourages users to
rethrow exceptions from one thread in another thread, producing misleading stack traces.
Additionally, it has a surprising policy about which exceptions to map and which to leave
untouched. Guava users who want a CheckedFuture can fork the classes for their own
use, possibly specializing them to the particular exception type they use. We recommend that
most people use ListenableFuture and perform any exception wrapping themselves. This
class is scheduled for removal from Guava in February 2018.

Store the Comparator alongside the Table. Or, if you know that the
Table contains at least one value, you can retrieve the Comparator with:
((SortedMap<C, V>) table.rowMap().values().iterator().next()).comparator();.

Creates a RateLimiter with the specified stable throughput, given as
"permits per second" (commonly referred to as QPS, queries per second), and a warmup
period, during which the RateLimiter smoothly ramps up its rate, until it reaches
its maximum rate at the end of the period (as long as there are enough requests to saturate
it).

End of Medium: A control character associated with the sent data which may be used to identify
the physical end of the medium, or the end of the used, or wanted, portion of information
recorded on a medium.

Invoked on a background thread after the referent has been garbage collected unless security
restrictions prevented starting a background thread, in which case this method is invoked when
new references are created.

CheckedFuture cannot properly support the chained operations that are the
primary goal of ListenableFuture. CheckedFuture also encourages users to
rethrow exceptions from one thread in another thread, producing misleading stack traces.
Additionally, it has a surprising policy about which exceptions to map and which to leave
untouched. Guava users who want a CheckedFuture can fork the classes for their own
use, possibly specializing them to the particular exception type they use. We recommend that
most people use ListenableFuture and perform any exception wrapping themselves. This
class is scheduled for removal from Guava in February 2018.

CheckedFuture cannot properly support the chained operations that are the
primary goal of ListenableFuture. CheckedFuture also encourages users to
rethrow exceptions from one thread in another thread, producing misleading stack traces.
Additionally, it has a surprising policy about which exceptions to map and which to leave
untouched. Guava users who want a CheckedFuture can fork the classes for their own
use, possibly specializing them to the particular exception type they use. We recommend
that most people use ListenableFuture and perform any exception wrapping
themselves. This class is scheduled for removal from Guava in February 2018.

File Separator: These four information separators may be used within data in optional fashion,
except that their hierarchical relationship shall be: FS is the most inclusive, then GS, then
RS, and US is least inclusive.

Group Separator: These four information separators may be used within data in optional fashion,
except that their hierarchical relationship shall be: FS is the most inclusive, then GS, then
RS, and US is least inclusive.

Returns a hash function implementing the Message Authentication Code (MAC) algorithm, using the
MD5 (128 hash bits) hash function and a SecretKeySpec created from the given byte array
and the MD5 algorithm.

Returns a hash function implementing the Message Authentication Code (MAC) algorithm, using the
SHA-1 (160 hash bits) hash function and a SecretKeySpec created from the given byte
array and the SHA-1 algorithm.

Returns a hash function implementing the Message Authentication Code (MAC) algorithm, using the
SHA-256 (256 hash bits) hash function and a SecretKeySpec created from the given byte
array and the SHA-256 algorithm.

Returns a hash function implementing the Message Authentication Code (MAC) algorithm, using the
SHA-512 (512 hash bits) hash function and a SecretKeySpec created from the given byte
array and the SHA-512 algorithm.

CheckedFuture cannot properly support the chained operations that are the
primary goal of ListenableFuture. CheckedFuture also encourages users to
rethrow exceptions from one thread in another thread, producing misleading stack traces.
Additionally, it has a surprising policy about which exceptions to map and which to leave
untouched. Guava users who want a CheckedFuture can fork the classes for their own
use, possibly specializing them to the particular exception type they use. We recommend
that most people use ListenableFuture and perform any exception wrapping
themselves. This method is scheduled for removal from Guava in February 2018.

CheckedFuture cannot properly support the chained operations that are the
primary goal of ListenableFuture. CheckedFuture also encourages users to
rethrow exceptions from one thread in another thread, producing misleading stack traces.
Additionally, it has a surprising policy about which exceptions to map and which to leave
untouched. Guava users who want a CheckedFuture can fork the classes for their own
use, possibly specializing them to the particular exception type they use. We recommend
that most people use ListenableFuture and perform any exception wrapping
themselves. This method is scheduled for removal from Guava in February 2018.