Information to be exposed in interface files which is produced by the stg2stg passes.
Moduleghc-10.0.0.20260917GHC2024
GHC.Stg.EnforceEpt.TagSig
- 3 types
- 4 values
- Packageghc-10.0.0.20260917
- Exports7
- LanguageGHC2024
- LicenceBSD-3-Clause
- SourceTagSig.hs
The signature attached to a binding.
Instances4Eq, Outputable, Binary, OutputableBndr
Eq TagSigDefined in ghc-10.0.0.20260917 · GHC.Stg.EnforceEpt.TagSigOutputable TagSigDefined in ghc-10.0.0.20260917 · GHC.Stg.EnforceEpt.TagSigBinary TagSigDefined in ghc-10.0.0.20260917 · GHC.Stg.EnforceEpt.TagSigOutputableBndr (Id, TagSig)Defined in ghc-10.0.0.20260917 · GHC.Stg.EnforceEpt.TagSig
What we know about a runtime value.
Constructors
TagDunnoWe don't know anything about the tag.
TagTuple [TagInfo]An unboxed tuple with taginfo for each element.
TagEPTAn evaluated and properly tagged value. See Note [Evaluated and Properly Tagged].
TagBottomingBottom of the domain. See Note [Bottom functions are TagBottoming] in GHC.Stg.EnforceEpt.
Is the given binding known to be properly tagged (or irrelevant, as for unboxed values and bottoming computations)?
Is the given value-level tag known to be properly tagged? NB: unboxed tuples are *not* treated as tagged here; they are handled specially by the rewriter (which considers them already evaluated).