Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Ohm's Law algorithm added #3934
Conversation
This comment has been minimized.
This comment has been minimized.
I have work a lot on this file and again make new Pr this time i follow all the guidelines styling conventions now lets see what will happen?? |
Thank god i made my first ever github contribution, i was very difficult for a beginner, but i did it, jus please review it and merged it i will more happy if you will merged it thanks. |
Co-authored-by: xcodz-dot <[email protected]>
Co-authored-by: Christian Clauss <[email protected]>
But cclauss thank you so much showing interest in my code before you nobody even tell me the problems with my code thank you again and i will be add these changes as you tell me . |
So i got it what you suggest me is
|
Thanks for the heads up on that. I missed that detail and we should seriously consider if making a new root directory is the right thing to do. Would we consider this a |
If this really needs a new directory then I think it should be Thinking about it, we can keep the number of directories same by putting the |
There are tons of quantum algorithms that have nothing to do with physics. |
I would be OK with adding |
Let's fast-fail. |
result = {"voltage": float(current * resistance)} | ||
return result |
cclauss
Nov 25, 2020
•
Member
Simply remove variables that are created on one line and then deleted on the next line.
Suggested change
result = {"voltage": float(current * resistance)}
return result
return {"voltage": float(current * resistance)}
Simply remove variables that are created on one line and then deleted on the next line.
result = {"voltage": float(current * resistance)} | |
return result | |
return {"voltage": float(current * resistance)} |
cclauss
Nov 25, 2020
Member
Why do we cast as float()
on this branch but not on the other two branches?
Why do we cast as float()
on this branch but not on the other two branches?
erdum
Nov 25, 2020
Author
Contributor
Because if you divide two values its gives you float but not in case for the multiplication , and remember i give return type float in type hint
Because if you divide two values its gives you float but not in case for the multiplication , and remember i give return type float in type hint
result = {"current": voltage / resistance} | ||
return result |
cclauss
Nov 25, 2020
Member
Suggested change
result = {"current": voltage / resistance}
return result
return {"current": voltage / resistance}
result = {"current": voltage / resistance} | |
return result | |
return {"current": voltage / resistance} |
result = {"resistance": voltage / current} | ||
return result |
cclauss
Nov 25, 2020
Member
Suggested change
result = {"resistance": voltage / current}
return result
return {"resistance": voltage / current}
result = {"resistance": voltage / current} | |
return result | |
return {"resistance": voltage / current} |
It seems that the |
There's also This is my proposal:
|
And now i think you may don't want to add my contribution because i saw other PR just simple and you see it and just merged without any exception but with my case you nearly figured out every small detail, i don't think this is a great place for beginner to start with that's not the way to teach a beginner its just like you are boss and i am your employ, finally i just say what i realize is you have specific problem with me. |
Very disappointment not expecting from a person who has lot's of experience, i expecting kindness and good teaching attitude but not always people are good |
@erdum I think this PR is extremely close to being landed. I know it is a lot of work but we have a great repo here because we sweat the details. We were seriously overwhelmed by Hacktoberfest so we might have let thru things that were not at the highest level of quality but that is the exception, not the rule. Thanks massively for your hard work and patience. |
@cclauss if you all say to me before then i am not going to comment that but sorry if my words hutt you but i jus lost my patience . |
Patience is a fragile thing. Your algorithm is now part of the repo. Thanks for that! |
I am beginner to github its my first time ever contribution i don't even about the CI for testing my code i figured out by my own how to solve issue because my checks are failing but in first time i jus understand that the more your code is clean then more your code is to be good |
Agreed. Our high standards make this a difficult repo for beginners to contribute to but we are trying to help people to quickly learn things like testing, type hints, good variable names, f-strings because they can make code more readable and more reliable. Other repos can be easier to contribute to but this repo tries to teach best practices. |
yes I learned a lot from you and your repo thanks |
The thing that I love is that this is not my repo... It is our repo. Now that your algorithm is in the repo, you are part of the club. The |
Yes my next goal will be on kcl law, it is complicated so i will try to run it locally then i will make PR so you can test or debug my code |
Now i realize you are a very nice person actually, so sorry for the previous comments |
Describe your change:
Finnaly i did it now i hope all checks should be clear
Checklist:
Fixes: #{$ISSUE_NO}
.