AngouriMath
RewriteRule
Description
Summary
One rewrite, addressable on its own: what it matches, what it puts there instead, where it
is written and which way it moves.
is written and which way it moves.
Remarks
The distinction is what
#28 asks for — a
derivation that says which rewrite fired rather than which group of them — and what
#825 is about.
than written out a second time. That is deliberate and it is the whole design: the
on the hot path changes and the two forms cannot drift apart. Transcribing forty arms into
forty objects by hand would be forty chances to alter a pattern silently, and expressing
them through the runtime matcher in
Simplify(System.Int32) per rule set exchanged.
purpose. This paragraph used to say the tier was absent, on the argument that a rule's
tier is a claim somebody has to argue for and cannot be derived from syntax. That argument
is right and it is not a reason for the property to be missing: where the argument has been made, the claim needs somewhere to live. A rule written as data declares one, and the
two tiers are both well populated — most rules are
Sound — against every set in the registry declaring
SoundUnderAssumptions, so the per-rule tier says
something the per-set one cannot. The live counts are measured by
read off a
where silently copying the set's down would have said the opposite.
Members
Description
PropertyGrowth
PropertyGuardSource
PropertyIndex
PropertyName
PropertyNodeTypes
PropertyPatternSource
PropertyReplacementSource
PropertySoundness
PropertySource
PropertySourceLine
PropertyToString
Method
Angouri © 2019-2023 · Project's repo · Site's repo · Octicons · Transparency · 4378 pages online