:: a typeCtrl KGHC 9.10.3 · lts/ghc-9.10.x · 248f8f0 · 2026-10-05
Moduleghc-9.10.3GHC2021
How should we choose which constraints to quantify over?
ApplyMRApply the monomorphism restriction, never quantifying over any constraints
EagerDefaultingSee Note [TcRnExprMode] in GHC.Tc.Module, the :type +d case; this mode refuses to quantify over any defaultable constraint
NoRestrictionsQuantify over any constraint that satisfies pickQuantifiablePreds
Outputable InferModeDefined in ghc-9.10.3 · GHC.Tc.SolverType-check a thing that emits only equality constraints, solving any constraints we can and re-emitting constraints that we can't. Use this variant only when we'll get another crack at it later See Note [Failure in local type signatures]
Panics if we solve any non-equality constraints. (In runTCSEqualities we use an error thunk for the evidence bindings.)
Return (Just new_inerts) if the Givens are satisfiable, Nothing if definitely contradictory.
See Note [Pattern match warnings with insoluble Givens] above.
Return True if the Wanteds are soluble, False if not
Normalise a type as much as possible using the given constraints.
See Note [tcNormalise].
Simplify top-level constraints, but without reporting any unsolved constraints nor unsafe overlapping.