The current implementation of lyap for complex scalar arguments is incorrect. We can see this by comparing the result obtained using 1x1 matrices vs scalars:

julia> A = (1.0+2.0im)*ones(1,1);

julia> C = (3.0+4.0im)*ones(1,1);

julia> lyap(A, C)  # expected
1×1 Matrix{ComplexF64}:
 -1.5 - 2.0im

julia> lyap(A[1], C[1])  # wrong! 
-1.1 + 0.2im

julia> -C[1] / 2real(A[1])  

Currently we've implemented a bunch of functions and constraints in a "lazy evaluation" fashion, i.e., whenever we need something for a Style program, we implement it in Penrose. We're getting to the point where we should really have a more complete/comprehensive list (e.g., that users can call at will).

How do we come up with this list? One natural idea is to simply pick some libraries, and

It should be noted that it currently applies to all of the existing packages.

Current behavior:

.> view ##Nat

  ⚠️
  
  The following names were not found in the codebase. Check your spelling.
    ##Nat

.> names ##Nat

  😶
  
  I couldn't find anything by that name.

.> alias.type ##Nat Nat

  Done.

.> names ##Nat

  Type
  Hash:  ##Nat
  Names: Nat

.> view ##Nat

  -- Nat is built-in.

Desired behavior would be something like:

Motivation

Per discussion at https://scsynth.org/t/terminology-question/3372, using "stutter" this way is ableist and actually also not a good description of what these features even do. We should replace them with clearer and more inclusive alternatives.

Description of Proposed Feature

• Deprecate these functions and classes and replace them with new ones:
  • Dstutter
  • Pstutt

Should suppress --strict warnings.