Skip to content
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

BasicRule_Generic Circular Reasoning #421

Merged
merged 7 commits into from
Feb 7, 2023

Conversation

19690ao
Copy link
Collaborator

@19690ao 19690ao commented Jan 28, 2023

Description

Unlike most puzzles' basic/direct rules, the rules for short truth tables are either direct or indirect subclasses of an abstract class called BasicRule_Generic. This rule happened to have a self-justification bug, which happened to affect every single basic rule in STT.

Prof. Bram noticed the one that affected BasicRuleAtomic (#417), but that was one of many.

For example, using biconditional elimination:
bi-el-2
...and a less obvious example using or elimination:
and-elim-circ
Although this transition is invalid, this bug is the reason that one of those cells is validated even though they're both equally part of the problem.

TLDR: Many STT basic rules have been bugged, possibly since its creation. I tried it on my build of Legup from LMS back from last year's intro to logic course, and I was able to reproduce the same behavior

oldversbugstt

Closes #417

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Enhancement (improvement to an already existing feature)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

Checklist:

  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation (if applicable)
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

@charlestian23 charlestian23 self-requested a review February 2, 2023 14:33
Copy link
Collaborator

@charlestian23 charlestian23 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just pushed a change to dev that refactors a lot of files. Can you pull that onto your branch and fix any merge conflicts?

@charlestian23 charlestian23 self-assigned this Feb 5, 2023
@charlestian23 charlestian23 self-requested a review February 7, 2023 21:45
Copy link
Collaborator

@charlestian23 charlestian23 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes seem good!

@charlestian23 charlestian23 merged commit b32a355 into Bram-Hub:dev Feb 7, 2023
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.

2 participants