Tidal parse and type errors appear in GHCi while sound problems appear in the SuperCollider post window

Tidal routes errors through two distinct systems. Code sent from the editor to GHCi (the Haskell interpreter) produces parse errors or type errors in GHCi if the block is malformed — the previously-evaluated d1..d16 channel keeps playing, never silenced by a bad eval. Runtime sound problems (unknown synth name, sample not found) appear separately in the SuperCollider post window. Knowing which system to check first is the first diagnostic step.

Examples

A typo in a function name produces a GHCi ‘Variable not in scope’ error while the old pattern continues. A missing sample name produces a SC post warning while the block evaluates successfully in GHCi.

Assessment

Describe where Tidal parse errors versus missing-sample errors surface, and state what happens to the currently-playing pattern when a GHCi error fires.