Rename Ensure class to Contract to resolve naming conflicts #80
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.
Summary
This PR resolves issue #63 by renaming the
Ensureclass toContractto avoid naming conflicts with external libraries like Ensure.That.Problem
The existing
Ensureclass conflicts with the popularEnsure.Thatlibrary, making it difficult for users to use both libraries in the same project. The issue specifically mentioned that this conflict could complicate code translation to C++.Solution
Ensure→Contractacross the entire codebaseEnsureAlwaysExtensionRoot→ContractAlwaysExtensionRoot,EnsureOnDebugExtensionRoot→ContractOnDebugExtensionRootAPI Changes
Before:
After:
C++ Changes:
Testing
Breaking Changes
This is a breaking change that requires users to update their code from
EnsuretoContract. However, the API pattern and functionality remain exactly the same.Benefits
Contractis commonly used for assertion libraries)Fixes #63
🤖 Generated with Claude Code