UofT-DSI | Python - Assignment #1: Anagram Checker#2
Closed
hitechparadigm wants to merge 1 commit intomainfrom
Closed
UofT-DSI | Python - Assignment #1: Anagram Checker#2hitechparadigm wants to merge 1 commit intomainfrom
hitechparadigm wants to merge 1 commit intomainfrom
Conversation
hitechparadigm
added a commit
that referenced
this pull request
May 16, 2024
UofT-DSI | Python - Assignment #2: Efficacy Analysis of a Hypothetical Arthritis Drug
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)
I have created two functions to check whether strings are anagrams.
What did you learn from the changes you have made?
I learned how to write functions, convert strings to lists, and compare them.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
There is a very concise way to write the code. However, I was not sure if that would be acceptable without any explanation.
For instance:
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
Not really.
How were these changes tested?
I used print() to check the outcomes and check the data type.
I used more anagrams to check how the functions work.
A reference to a related issue in your repository (if applicable)
Checklist