Currently, the docs for the Printf standardlib simply mentions it uses "C printf style format specification", but does not specify what that is, nor provides a link to the C printf format.

It would be nice to explain it in the docs.

Since we migrated from the Haskell runtime (what's in master now) to a React + Typescript runtime that's part of the frontend (what's in web-runtime now), a lot of the example domains we implemented for the paper need to be ported to the new runtime.

This is high-priority for us since it will enable us to test that the new runtime is at parity, and start c

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

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