Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/coq-community/coq-ext-lib
A library of Coq definitions, theorems, and tactics. [maintainers=@gmalecha,@liyishuai]
https://github.com/coq-community/coq-ext-lib
coq coq-ci coq-platform library programming
Last synced: 27 days ago
JSON representation
A library of Coq definitions, theorems, and tactics. [maintainers=@gmalecha,@liyishuai]
- Host: GitHub
- URL: https://github.com/coq-community/coq-ext-lib
- Owner: coq-community
- License: bsd-2-clause
- Created: 2012-08-22T14:34:07.000Z (about 12 years ago)
- Default Branch: master
- Last Pushed: 2024-09-17T17:09:27.000Z (about 2 months ago)
- Last Synced: 2024-09-30T20:46:48.339Z (about 1 month ago)
- Topics: coq, coq-ci, coq-platform, library, programming
- Language: Coq
- Homepage: https://coq-community.org/coq-ext-lib/
- Size: 2.97 MB
- Stars: 128
- Watchers: 16
- Forks: 46
- Open Issues: 17
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-coq - ExtLib - Collection of theories and plugins that may be useful in other Coq developments. (Projects / Libraries)
README
# coq-ext-lib
[![Docker CI][docker-action-shield]][docker-action-link]
[![Contributing][contributing-shield]][contributing-link]
[![Code of Conduct][conduct-shield]][conduct-link]
[![Zulip][zulip-shield]][zulip-link]
[![coqdoc][coqdoc-shield]][coqdoc-link]
[docker-action-shield]: https://github.com/coq-community/coq-ext-lib/actions/workflows/docker-action.yml/badge.svg?branch=master
[docker-action-link]: https://github.com/coq-community/coq-ext-lib/actions/workflows/docker-action.yml
[contributing-shield]: https://img.shields.io/badge/contributions-welcome-%23f7931e.svg
[contributing-link]: https://github.com/coq-community/manifesto/blob/master/CONTRIBUTING.md
[conduct-shield]: https://img.shields.io/badge/%E2%9D%A4-code%20of%20conduct-%23f15a24.svg
[conduct-link]: https://github.com/coq-community/manifesto/blob/master/CODE_OF_CONDUCT.md
[zulip-shield]: https://img.shields.io/badge/chat-on%20zulip-%23c1272d.svg
[zulip-link]: https://coq.zulipchat.com/#narrow/stream/237663-coq-community-devs.20.26.20users
[coqdoc-shield]: https://img.shields.io/badge/docs-coqdoc-blue.svg
[coqdoc-link]: https://coq-community.org/coq-ext-lib
A collection of theories and plugins that may be useful in other Coq developments.
## Meta
- Author(s):
- Gregory Malecha (initial)
- Coq-community maintainer(s):
- Gregory Malecha ([**@gmalecha**](https://github.com/gmalecha))
- Yishuai Li ([**@liyishuai**](https://github.com/liyishuai))
- License: [BSD 2-Clause "Simplified" License](LICENSE)
- Compatible Coq versions: Coq 8.11 or later or 8.9
- Additional dependencies: none
- Coq namespace: `ExtLib`
- Related publication(s): none
## Building and installation instructions
The easiest way to install the latest released version of coq-ext-lib
is via [OPAM](https://opam.ocaml.org/doc/Install.html):
```shell
opam repo add coq-released https://coq.inria.fr/opam/released
opam install coq-ext-lib
```
To instead build and install manually, do:
``` shell
git clone --recurse-submodules https://github.com/coq-community/coq-ext-lib.git
cd coq-ext-lib
make theories # or make -j theories
make install
```
Ideas
-----
- Embrace new features, e.g. universe polymorphism, primitive projections, etc.
- Use modules for controlling namespaces.
- Use first-class abstractions where appropriate, e.g. type classes, canonical structures, etc.
- The library is mostly built around type clases
- Notations should be hidden by modules that are explicitly opened.
- This avoids clashes between precedence.
- TB: Actually, this does not completely avoid clashes, if we have to open two modules at the same time (for instance, I often need to open Equality, to get dependent destruction, which conflicts with the rest of my development)
- TB: I like the idea of having to prefix operations by the name of the module (e.g., DList.fold, DList.map, DList.T), and yet to benefit from the support of notations, without opening this module. I implement that by having a module DList that contains the operations, inside the file DList. The notations live in the file DList, and I do Require Import DList everywhere...
- Avoid the use of the 'core' hint database.
- Avoid the use of dependent functions, e.g. dependendent decidable equality,
in favor of their boolen counter-parts. Use type-classes to expose the proofs.
-
File Structure
--------------
* theories/
- Base directory to the provided theories