Fix: Resolve macOS filename collision between Clause.rkt and clause.rkt #666
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.
Problem
This PR fixes issue #663 - Case-Insensitive Filesystem Collision on macOS: Clause.rkt vs clause.rkt in satore/
On case-insensitive filesystems (macOS and Windows), having both
Clause.rktandclause.rktin the same directory causes file collisions, making it impossible to clone or work with the repository on these systems.Solution
Renamed
Clause.rkttoclause-struct.rktto:clause.rkt(which contains basic clause operations)Changes Made
satore/clause-struct.rktwith the content fromClause.rktsatore/Clause.rktsatore/saturation.rkt(line 22): Changedsatore/Clause→satore/clause-structsatore/rewrite-tree.rkt(line 15): Changedsatore/Clause→satore/clause-structsatore/unification-tree.rkt(line 21): Changedsatore/Clause→satore/clause-structTesting
The code should work identically to before, as only the filename and import paths have changed, not the functionality. All imports have been updated to reference the new filename.
Impact
clause-struct.rktbetter describes the file's contents (Clause struct definition with additional properties)Fixes #663