agda/agda-stdlib

#1332

· jespercockx opened

on Oct 23, 2020

Increasing the amount of re-exporting in <code>Data.X</code>

library-design

question

#619

· mechvel opened

on Feb 15, 2019

Use instance fields for superclasses (?)

discussion

instances

#1529

· jespercockx opened

on Jun 27, 2021

Add structures/bundles for pairs of strict and non-strict orders

discussion

library-design

#1179

· MatthewDaggitt opened

on Apr 29, 2020

There should be level-polymorphic versions of the combinators in <code>Data.List.Categorical</code>

addition

#951

· laMudri opened

on Oct 18, 2019

generic Nonzero proposal

addition

#1175

· mechvel opened

on Apr 28, 2020

Improvements to <code>Relation.Binary.Rewriting</code>?

#2081

· jamesmckinna opened

on Sep 9, 2023

names of things (vol. 94): <code>Relation.Nullary.Reflects</code>

#2058

· jamesmckinna opened

on Aug 15, 2023

Reconciling <code>Data.Nat.Divisibility.Core._∣_</code> and <code>Algebra.Definitions.RawMagma._∣_</code>

#2115

· jamesmckinna opened

on Sep 29, 2023

Consider where we can use <code>opaque</code> mechanism to provide abstraction

breaking

library-design

#2136

· MatthewDaggitt opened

on Oct 12, 2023

Standardisation of folds

library-design

naming

question

#278

· MatthewDaggitt opened

on Apr 13, 2018

Misnomer: <code>Relation.Binary.Definitions.Total</code>

library-design

naming

question

#453

· WolframKahl opened

on Sep 5, 2018

AlmostCancellative in Nat.Properties ?

refactoring

#1562

· mechvel opened

on Jul 26, 2021

Standardise implicit arguments of cancellation properties.

breaking

refactoring

#1436

· astrainfinita opened

on Feb 23, 2021

Inconsistent naming between <code>Data.(Nat/Integer).Properties</code>

bug

naming

#1579

· MatthewDaggitt opened

on Aug 12, 2021

Should StrictTotalOrder be decidable?

library-design

question

#452

· HuStmpHrrr opened

on Sep 5, 2018

List of wrinkles in <code>Data.List.Properties</code>

breaking

refactoring

#2358

· MatthewDaggitt opened

on Apr 11, 2024

[DRY] why is <code>_≉_</code> defined both for <code>Algebra.Bundles.Raw.RawX</code> bundles, and via <code>Setoid</code> instances, for <code>Algebra.Bundles.X</code>?

library-design

refactoring

#2274

· jamesmckinna opened

on Feb 3, 2024

Splitting <code>Data.Char.Base</code>

discussion

library-design

#1489

· JacquesCarette opened

on Apr 25, 2021

Find all single letter publicly-exported modules and make sure they are private

breaking

bug

#2472

· MatthewDaggitt opened

on Sep 3, 2024

[DRY] Refactor algebraic properties of types

#2489

· jamesmckinna opened

on Oct 1, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

v3.0

Add type classes and <code>.Instance</code> modules declaring their instances

Increasing the amount of re-exporting in <code>Data.X</code>

Use instance fields for superclasses (?)

Add structures/bundles for pairs of strict and non-strict orders

There should be level-polymorphic versions of the combinators in <code>Data.List.Categorical</code>

generic Nonzero proposal

Improvements to <code>Relation.Binary.Rewriting</code>?

names of things (vol. 94): <code>Relation.Nullary.Reflects</code>

Reconciling <code>Data.Nat.Divisibility.Core._∣_</code> and <code>Algebra.Definitions.RawMagma._∣_</code>

Consider where we can use <code>opaque</code> mechanism to provide abstraction

Standardisation of folds

Misnomer: <code>Relation.Binary.Definitions.Total</code>

AlmostCancellative in Nat.Properties ?

Standardise implicit arguments of cancellation properties.

Inconsistent naming between <code>Data.(Nat/Integer).Properties</code>

Should StrictTotalOrder be decidable?

remove everything deprecated from v1.3 (and before)

List of wrinkles in <code>Data.List.Properties</code>

[DRY] why is <code>_≉_</code> defined both for <code>Algebra.Bundles.Raw.RawX</code> bundles, and via <code>Setoid</code> instances, for <code>Algebra.Bundles.X</code>?

Splitting <code>Data.Char.Base</code>

Fix #2396 by removing redundant zero in IsNonAssociativeRing

Vec.Properties: drop eq parameter when it is a property (v3.0 changes)

Rename <code>homo</code> to <code>∙-homo</code> in <code>Algebra.Morphism.Structures</code>

Find all single letter publicly-exported modules and make sure they are private

[DRY] Refactor algebraic properties of types

v3.0

List view