jamesmckinna
jamesmckinna
Fixes #2471 Lots of (trivial) knock-on viscosity: PR takes the opportunity to rename/refactor proofs in (hopefully!) helpful ways. Is this v2.x or v3.0, because `breaking`?
See [this comment](https://github.com/agda/agda-stdlib/issues/2502#issuecomment-2613113410) on issue #2502 . By analogy with `Algebra.Definitions` and `Algebra.Structures`... moreover `non-breaking`. Indeed, `Base` is only imported by `Algebra.Consequences.Setoid` (and by the now-deprecated module `Algebra.FunctionProperties.Consequences.Core`), so there...
[ refactor ] Redefine `Relation.Binary.Definitions.Adjoint`, plus knock-on `Function.Consequences`
Fixes #2581 .
This lifts out the refactoring aspects of #2572 and should be merged first of the two. It also rectifies two bugs * use of deprecated names in `Data.Rational.Unnormalised.Properties` * changing...
The trouble with [the definition](https://github.com/agda/agda-stdlib/blob/2bce915db17fc284c7ed7a13d91cffe7a058a1e1/src/Algebra/Consequences/Setoid.agda#L311-L325): ```agda ------------------------------------------------------------------------ -- Without Loss of Generality module _ {p} {P : Pred A p} (≈-subst : Substitutive _≈_ p) (∙-comm : Commutative _∙_) where...
These modules are structured around: * `Base`, depending only on the underlying `Carrier` set `A`, whose properties make explicit a dependency on a(n equality) relation `_≈_ : Rel A ℓ`;...
Variations on the theme of uncoupling from `Data.Product.Base`, lifted out from #2579 : cf. #207 * `bug`: we don't give fixities to the various uses of `_,_` as a constructor...
Meditating on #2580 (and some other recent PRs, including those which touch `Function.*`), it's hard not to observe the following: * `Relation.Binary.Definitions.Adjoint` universally quantifies the product of two implications, rather...
```quote * the PR itself draws attention to the fact that `Symmetric _#_` is in fact a redundant part of the definition of `IsHeytingCommutativeRing`, so it *might* be worth having...
This is a long-standing legacy issue (cf. #1099 ) that causes problems esp. regarding: * the dependency graph: `Data.List.Base` and `Properties` need to import `Data.Nat.Divisibility` otherwise unnecessarily; also, how much...