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.

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

Should suppress --strict warnings.

Description:
When:

1. A function in a service processRequest...
2. Calls another function in the same service createError...
3. That returns an error...
4. The processing in the first function processRequest exits prematurely (as if it were doing a check). This behaviour is not the subject of this issue report. Issue #24795 is.
5. The reason of the error has its first letter Lo

let _r = 1
let _r = 2

This code runs with this failure.

** (MatchError) no match of right hand side value: 1

I think it's making erlang code that looks like the following.

_R = 1
_R = 2

Suggestion / feature request: List which languages / compilers support source maps, and which do not.