Make std.string.removechars @safe and pure
Make std.string.removechars @safe and pure by using implicit conversion
Fix emplace
Fix spelling
Issue 9559 - Range of Nullable doesn't work with std.array.array
Tweak emplace some
emplace: diagn for quals; simplf alias this brnch
make "emplace(singleArg)" safe pure nothrow
reword emplace deprecation message
Yet another emplace unittest that is fixed
Add RefRange to ddoc overview.
Merge pull request #1520 from tom-tan/safe-pure-string-removechars

Make std.string.removechars @safe and pure
lookbehind for ctRegex
Partial fix for Issues 7067 and 10434 - std.random.RandomCover

The existing RandomCover design is fatally flawed because it
requires a RNG as input, which it then copies internally by
value.  So, unless the user is smart enough to pass something
like e.g. SomeRNG(unpredictableSeed), there will be unintended
correlations in random behaviour.

This partial fix follows the design of RandomSample in allowing
RandomCover to use the thread-global default RNG rndGen.  It
also improves the choice of template parameter and variable
names in line with Issue 10434.
Partial fix for Issue 10434 - std.random.RandomSample

In line with changes to RandomCover, this patch tweaks
the choice of template parameter and variable names in
order to bring clarity and uniformity to the module.
Correct the .save methods for RandomCover and RandomSample.

RandomCover and RandomSample should only be save'able if:

   * the input is a forward range

   * the thread-global RNG rndGen is not being used

   * the RNG being used is a forward range.
Unittests for RandomCover and RandomSample should test with all RNG types.
Documentation updates for RandomCover and RandomSample.

Mostly regarding the statistical safety-related concerns
when passing a specified RNG, plus a few corrections.
Small stylistic tweaks for Andrei :-)
Ensure bool[] _chosen is filled with false at start of cover.