How do I use verbose or debug compilation modes?

  -E0    Minimal: single-line error messages with location and code
  -E1    Visual: Rust-style display with source snippets and caret markers
  -E2    Suggestions: visual plus 'Did you mean?' fuzzy matching
  -E3    Full: detailed explanations with diagnosis, rationale, and examples

  -c     Incremental compile (only recompile changed files)
  -C     Full recompile (recompile everything from scratch)
  -r name   Which program to run, when the EK9 file defines more than one
  -t     Run tests (@Test methods and expected_output.txt)

  -v     Verbose output: shows which files are being compiled and which phases complete
  -dv    Debug verbose: more detail including symbol resolution and phase timing
  -cg    Compile with debugging information, so 'ek9 -d <port>' and 'ek9 -dap' can step through EK9 source
  -cd    Combined development and debug mode

  -di    DI/AOP analysis: outputs dependency injection wiring and aspect pointcut information
  -Cp PHASE  Stop at the named phase (for example -Cp PRE_IR_CHECKS, not a number): compiles up to that phase and stops. Not typical for end users, but valuable for AI tools learning EK9 (verify syntax and types compile correctly without generating runnable programs) and for compiler developers

  -h keyword    Help for a built-in type (e.g., 'ek9 -h String', 'ek9 -h List')
  -h EXXXXX     Explain a specific error code
  -H            List all available help keywords
  -V            Show compiler version

  -t, -t1   Human-readable test output (the default)
  -t0       Terse output, a minimal summary for scripting
  -t2       JSON output, for tools and AI
  -t3       JUnit XML output, for CI/CD integration
  -t4       Detailed coverage report listing what is uncovered
  -t5       Verbose coverage report listing what is covered and uncovered
  -t6       Interactive HTML coverage report

  -tC    Display coverage results after the tests have run
  -tp    Add profiling (call counts and durations) to the test run; -t2p and -t6p give JSON and an HTML flame graph

defines module qa.debugging.verbosemodes

  defines function

    describeFeature()
      ->
        featureEnabled as Boolean
        featureName as String
      <- description as String: String()

      if featureEnabled
        description: `${featureName} is enabled`
      else
        description: `${featureName} is disabled`

  defines program

    VerboseModesDemo()
      stdout <- Stdout()

      // Simple program to demonstrate compilation
      stdout.println("Compilation modes demo")

      // Use string interpolation
      version <- "1.0"
      stdout.println(`Version: ${version}`)

      // Simple arithmetic
      a <- 10
      b <- 20
      stdout.println(`Sum: ${a + b}`)

      // Boolean check via function parameter
      stdout.println(describeFeature(true, "Logging"))

      // List operations
      items <- ["alpha", "beta", "gamma"]
      for item in items
        stdout.println(`Item: ${item}`)

featureDesc <- describeFeature(true, "Logging")

stdout.println(describeFeature(true, "Logging"))