Right now toSplitInto uses display: false for all tests.

See this issue sympy/sympy#11044 . That issue was fixed in PR sympy/sympy#11566. Though no test case was added for the lambdify.

What needs to be done?

Add test case that this works just fine:

>>> from sympy import MatrixSymbol, lambdify
>>> x = MatrixSymbol('x', 3, 1)
>>> f = lambdify(x, x.T*x)

Test case needs to

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;

Encryption is an awesome start, thank you @opensource21 and @gsantner for getting this in. For me, this was a critical feature.

The existing feature addresses the data at rest encryption. This feature request is to make "locking" easy. This allows one to let someone else use their phone for a few minutes, unsupervised, without fear that private

When using jupyter notebooks, currently a lot of space is occupied by the output images, and sometimes it is nice to have things a bit tighter together.
Here a current screenshot (even with the lowest quality):

For comparison:
The standard output size for matplotlib is 375 × 248 pixe

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