refactor(Propositional/Kripke): Forcing Relation#674
Draft
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Logic.ForcingRelationに寄せようと思って色々修正してみているが，grindなどが結局Logic.ForcingRelation側の定義では上手く行われず実際の充足関係の定義にもう一度当てるという二度手間が発生するなど，おそらく上手くいかないような気がする．あるいは，意味論側でモデルという概念を忘れてフレームと付値のみで議論する（そのように充足関係を定義する）というのがおそらく良い解決案なのかもしれない．色々試してみる．