Skip to content

Upstream dependencies for Infinite Descent section 2.1 #128

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 12 commits into
base: main
Choose a base branch
from

Conversation

pimotte
Copy link
Contributor

@pimotte pimotte commented Apr 30, 2025

This is the upstreaming of some work of @cyborggeneraal.

Stuff that was needed:

  • Avoid sumbool and sigma type notations, as they conflict with set notation
  • Magic with notation to make stuff work

TODO:

  • Make characterizations work both ways (@jim-portegies Is this just a matter of making it an if-and-only-if? How should I add it in the database?)
  • Write more tests

@jim-portegies
Copy link
Contributor

As an answer to the question above: I think we often add one side of the implication to the automation system. But sometimes we even add both. But it may not be the best design, as it may create loops. At the same time, I think our automation system has some detection of loops.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants