Define path equivalence #228
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Blaisorblade
force-pushed
the
path-equiv
branch
2 times, most recently
from
3b78a43
to
daa6936
Compare
Blaisorblade
force-pushed
the
path-equiv
branch
4 times, most recently
from
37b39ee
to
c45d4b8
Compare
Blaisorblade
added a commit
that referenced
this pull request
Dec 27, 2021
Very different from #228. But using 1 environment seems wrong, on paper I use 2 (even if in some places I can only use 1).
Blaisorblade
added a commit
that referenced
this pull request
Dec 29, 2021
Very different from #228. But using 1 environment seems wrong, on paper I use 2 (even if in some places I can only use 1).
Blaisorblade
added a commit
that referenced
this pull request
Dec 30, 2021
Very different from #228. But using 1 environment seems wrong, on paper I use 2 (even if in some places I can only use 1).
Blaisorblade
added a commit
that referenced
this pull request
Jan 10, 2022
Very different from #228. But using 1 environment seems wrong, on paper I use 2 (even if in some places I can only use 1).
Blaisorblade
added a commit
that referenced
this pull request
Jan 29, 2022
Very different from #228. But using 1 environment seems wrong, on paper I use 2 (even if in some places I can only use 1).
Blaisorblade
added a commit
that referenced
this pull request
Jan 30, 2022
Very different from #228. But using 1 environment seems wrong, on paper I use 2 (even if in some places I can only use 1).
Blaisorblade
added a commit
that referenced
this pull request
Feb 27, 2022
Very different from #228. But using 1 environment seems wrong, on paper I use 2 (even if in some places I can only use 1).
Blaisorblade
added a commit
that referenced
this pull request
Aug 11, 2022
Very different from #228. But using 1 environment seems wrong, on paper I use 2 (even if in some places I can only use 1).
Blaisorblade
added a commit
that referenced
this pull request
Aug 27, 2022
Very different from #228. But using 1 environment seems wrong, on paper I use 2 (even if in some places I can only use 1).
Blaisorblade
added a commit
that referenced
this pull request
Aug 27, 2022
Very different from #228. But using 1 environment seems wrong, on paper I use 2 (even if in some places I can only use 1).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Attempt defining when two paths are "equivalent", that is, all the types they contain are equal (and any other definitions coincide), and showing that all semantic types respect this equivalence. Finishing this might take around a couple of days and ~1000 lines of code.
Annoyingly, singleton types don't respect that equivalence; fixing that might be quite bothersome, but maybe we needn't.