ChucK compile errors block shred addition while runtime errors remove only the offending shred

ChucK has two distinct error modes with different consequences. Compile-time errors (type-check, parse) report a line reference and prevent the shred from being added to the VM — the existing running shreds keep playing unaffected. Runtime errors (null-pointer, array out-of-bounds) remove only the offending shred but leave all other shreds running. A third class — silent failures — produces no error at all and is the hardest to debug. Understanding which class you face determines the recovery action.

Examples

A type mismatch on => produces a compile error and the shred is not added. An array-out-of-bounds during play removes that shred at runtime; the other voices keep sounding.

Assessment

Given a ChucK bug, classify it as compile-time, runtime, or silent failure, and state which shreds survive each class.