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
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.
What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Implemented an anagram checker in two stages: a base version (case-insensitive) and an extended version with a boolean parameter to control case sensitivity.
What did you learn from the changes you have made?
Improved understanding of string normalization, sorting for comparison, and designing functions with configurable behavior.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
Considered using collections.Counter to compare character frequencies as an alternative to sorting.
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
Clarifying when to apply case normalization based on the boolean flag. Resolved by aligning the logic with the requirement.
How were these changes tested?
Validated using provided examples and additional test cases with varying letter casing to ensure correct behavior.
A reference to a related issue in your repository (if applicable)
N/A
Checklist