option to ignore warnings during development:

[waalge]

What is your idea? Provide a use case.

Early dev flow: make function with signatures, but no body. Start to fill them out.

fn func0(
  arg00: Typ00,
  arg01: Typ01,
  arg02: Typ02,
  arg03: Typ03,
) -> Typ0 { 
  fail @"todo"
}

fn func1(
  arg00: Typ10,
  arg01: Typ11,
  arg02: Typ12,
  arg03: Typ13,
) -> Typ1 { 
  fail @"todo"
}

fn func2(
  arg00: Typ20,
  arg01: Typ21,
  arg02: Typ22,
  arg03: Typ23,
) -> Typ2 { 
  fail @"todo"
} 

(Using fail @"todo" rather than todo @"stuff" supresses a line of output, and is sufficiently clear of its intent. )

Why is it a good idea?

Test some part of code

 Summary 2 errors, 132 warnings

ummmm.

Another suggestion: If the code sees a todo then condense all warnings of unused variable into I'm assuming you'll get around to using these variables when you do that todo

What is the current alternative and why is it not good enough?

Wading through irrelevant console output. LSP super noisy.

[rvcas]

Yea we've been meaning to have a less verbose mode. Maybe it's about time.

[KtorZ]

Note: warnings are printed on stderr whereas errors are printed on stdout. So you can simply redirect the output as such to get rid of warnings, while keeping errors:

 aiken check 2>/dev/null