1lab/mikan
13
52
Fork
You've already forked mikan
9

Full support for Indexed Inductive-Recursive Types in Mikan #105

Open
opened 2026年05月19日 07:19:58 +02:00 by EmberEdison · 1 comment

Even though the devs have been trying to fix legacy baggage by cutting features from Cubical Agda, it'd be awesome if we could also fix things by adding features instead.

I'm officially petitioning to get full support for Indexed Inductive-Recursive Types added to Mikan.

Map

  • Full support for Inductive Families
  • Full support for Inductive-Recursive Types
  • Full support for Indexed Inductive-Recursive Types

References

Even though the devs have been trying to fix legacy baggage by cutting features from `Cubical Agda`, it'd be awesome if we could also fix things by adding features instead. I'm officially petitioning to get full support for `Indexed Inductive-Recursive Types` added to `Mikan`. # Map * Full support for `Inductive Families` * Full support for `Inductive-Recursive Types` * Full support for `Indexed Inductive-Recursive Types` # References * [Proper support for inductive families in Cubical Agda](https://github.com/agda/agda/issues/3733) * [Canonicity for Indexed Inductive-Recursive Types](https://andraskovacs.github.io/pdfs/ir_canonicity.pdf)

By "full support", do you mean the removal of UnsupportedIndexedMatch warnings? This is certainly on the roadmap, but is not currently a high-priority task.

By "full support", do you mean the removal of `UnsupportedIndexedMatch` warnings? This is certainly on the roadmap, but is not currently a high-priority task.
Sign in to join this conversation.
No Branch/Tag specified
main
aliao/occurs-opt
aliao/rec-con
fix-license
aliao/oopsie
aliao/strengthen-iapply
No results found.
Labels
Clear labels
1 - scope
language
 Backwards-compatible changes to the surface language, such as adding new features.
1 - scope
language change
 Breaking changes to a documented part of the surface language. These should be documented and specifically called out in the changelog.
1 - scope
performance
 Semantics-preserving performance work.
1 - scope
task
 Changes that are not apparent to the user, e.g. developer documentation and refactors, which do not need to be documented.
A: dead-code
Dead code elimination and --save-metas.
A: errors
Reporting of error and warning messages.
A: highlighting
Highlighting during interaction & literate compilation
A: imports
Handling of imports and interface file de/serialization.
A: infra
Iinfrastructure (e.g. CI, developer documentation, the build system, or the repository itself)
A: instance
Instance declarations, arguments, and resolution
A: lhs
LHS checking, coverage checking, and clause compilation
A: modules
Declaration and instantiation of parametrised modules.
A: parallel
Parallel typechecking.
A: positivity
Positivity checking
A: printing
Pretty-printing, display forms, and the wording of diagnostic messages
A: records
Record declarations, record expressions and copattern matching
A: scoping
Scope checking (ConcreteToAbstract)
A: termination
Termination checking
0 - type
bug
 Issues describing an incorrect behaviour in the project, typos in the documentation, etc.
0 - type
discussion
 An issue raised to gather opinions on a proposed change, or a suggested language change.
0 - type
question
 An issue raised to ask a question.
9 - status
duplicate
 This issue or pull request already exists.
9 - status
info needed
 More information is needed from the submitter to decide how to proceed with the issue report.
9 - status
invalid
 The issue report or pull request does not describe an actual bug, or does otherwise does not meet the contributing guidelines.
good first issue
Interested in contributing? Get started here.
upstream
Related to an upstream repository, already reported there
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
1lab/mikan#105
Reference in a new issue
1lab/mikan
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?