Consolidate Polysemy.Plugin configuration to cabal ghc-options

[Copilot]

Description

Polysemy.Plugin was configured inconsistently across the codebase via both per-file OPTIONS_GHC pragmas and cabal ghc-options. This standardizes on cabal-level configuration.

Changes:

• Removed {-# OPTIONS_GHC -fplugin=Polysemy.Plugin #-} from 32 source files (29 in spar, 3 in polysemy-wire-zoo)
• Added -fplugin=Polysemy.Plugin to ghc-options in:
  • spar.cabal: library, test-suite spec, executable spar-integration
  • polysemy-wire-zoo.cabal: library, test-suite spec

Before:

{-# OPTIONS_GHC -fplugin=Polysemy.Plugin #-}

module Spar.API where

After:

module Spar.API where

library
  ghc-options: ... -fplugin=Polysemy.Plugin

Checklist

• Add a new entry in an appropriate subdirectory of changelog.d
• Read and follow the PR guidelines

Original prompt

There are two ways to enable the Polysemy.Plugin GHC compiler plugin in our project:

• By adding ghc-options: -fplugin=Polysemy.Plugin to .cabal files
• By adding a language extension to .hs source files: `{-# OPTIONS_GHC -fplugin=Polysemy.Plugin #-}

We want to unify this.
Please,

• remove all {-# OPTIONS_GHC -fplugin=Polysemy.Plugin #-} language extensions from Haskell source files
• Add -fplugin=Polysemy.Plugin to all ghc-options Cabal file sections that related to modules which are using/importing Polysemy.
• ensure there are no duplicate entries of -fplugin=Polysemy.Plugin in ghc-options Cabal file sections

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.