We already have a function _searchindex to search for subsequences of byte arrays. It would be nice to expose this by adding corresponding methods to findfirst and findnext.

Although the current _seardhindex implementation only accepts Vector arguments, it looks like t

Currently, labels are placed in a very ad-hoc manner, by applying repel/atDist/etc objectives and constraints in a very brittle way in the Style program. The goal is to come up with a general, fast, flexible, label-specific layout strategy that also works with the rest of the diagram.

It is easy to get started with some small existing Penrose diagrams, and working to improve their labeling

➜ corral --help=false
ERRR: Error: missing subcommand at: 'corral'

and yet...

Options:
   -g, --debug=0             Configure debug output: 0=off, 1=err, 2=warn, 3=info, 4=fine.
   -n, --nothing=false       Don't actually apply changes.
   -h, --help=false

according to the options, that should work.

Options shouldn't have "=false" as the default displayed really.

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

In supercollider/supercollider#4572 we discussed the need for better documentation on when collection functions test on equality vs identity. For instance, SequenceableCollection:indexOf tests on identity, but you wouldn't know it f

Really nice project.

Writing in coconut files, you lose all the IDE integrations for Python. For example, I use VSCode and all the intellicode and hints of course doesn't work for cocount.

I am not too familiar but perhaps theres needs to be a separate language server or maybe you could leverage the existing Python integrations. Either way, better IDE integration wo