The version of flow-typed for Jest is v24.x.x, but we use v26.

The following behavior was introduced in 1.7.

simplify in some circumstances transforms sign(x) into a Piecewise involving x / Abs(x); somehow this transformed expression can lead to incorrect solutions from solve and solveset.

Consider, e.g., f(x) = x * sign(x), which has a zero at x == 0. After simplifying, even though the Piecewise function explicitly states the case `f

I've been treating tuShorten/tuWiden as a string-ish conversion between UTF16 and UTF 8, so I recommend this.

Here's the code; add it to the end of every tuShorten/tuWiden function.
if (out < (original_out + out_len)) out = 0;

Description

Presently, the user is allowed to pick colors for BG and FG using a color wheel. While this is handy when exploring new colors, this is actually hard to use when the user already has a specific hex code in mind and would just like to enter it

IEEE 754 recommends (but does not require) a compound function, which is in the process of being standardized for C and C++; we should expose it in swift-numerics. The simplest, most literal translation of the operation into Swift would be:

extension RealFunctions {
  /// (1+x)ⁿ
  /// 
  /// Returns NaN if x < -1.
  static func compound(_ x: Self, _ n: Int) -> Self {
    // not