[Eliud’s Eggs] Add approaches#4232
Conversation
|
@BethanyG, the PR should be ready for review now. I ended up leaving recursion and regexes out, as recursion isn't that relevant for an exercise linked to the |
|
I think Microsoft went and "Microsofed" all over this. I think you can find "closing words" under the |
|
The |
|
I have meetings this afternoon, but will get to reviewing ASAP after that. THANK YOU SO MUCH FOR THIS!!. I know it was a TON of work. Much appriciated. 😄 |
|
Sorry to be so quite. I have been really swamped. |
It's fine, I know life sometimes does that 😅
I can see the development section now, but I'm not sure if it was there before? I don't think I can edit any of the things in the bar on the right-hand side though, so it's probably a permissions thing. |
also add more links to the docs for built-in functions
use "conditional expression" as the main name, and only mention "ternary operator" as another name for a "conditional expression"
Courtesy of [this conversation in issue 4227][exercism#4227 (comment)]
e446e4a to
909ca84
Compare
|
CRAP. I just used the GH CLI and it removed ALL of my edits. That's 4 hours worth of work ... gone. I am going to try and back up and fix it. I hope I can. |
|
😱 I really hope it can be fixed... |
|
I got he changes back, but I have renamed some files. I think the safest thing to do is to save out your most recent changes elsewhere, let me re-commit my changes, then we can re-apply your most recent ones. Does that sound OK to you? |
Directories and file links using 'Parameter' were renamed to 'Argument'. This is because parameters are when you write a function or class. Arguments are used when a function is *called*.
|
Alright. I think (I hope and I pray) that things are resolved. That will teach me to trust that gh CLI will do the right thing. UGH. Apologies for making changes directly instead of suggesting. There was enough to review that I decided to pull it locally -- but there's no mechanism for then "suggesting". My recommendation is to give it a quick read-over, and if you hate the changes I've made (or I have borked yours), you can overwrite them, or ask me to revert them. An explanation about changing |
|
AARG. Looks like to really see the changes, you have to look at the individual commits. Dang. I am *SO SORRY). |
It seems like it's worth it to change them to
Hmm... I think I have a way to avoid that 😄 |
A lot of times it's sorta a distinction without a difference ...until you get into all the crazy-pants stuff Python does with I am NOT looking forward to writing up the concept on those. ;-) |
|
Yeah... That sounds like quite an ordeal. At least the basics of variable ones were already covered by "Unpacking And Multiple Assignment", and type-hints could be a separate concept. |
|
Type-hints will certainly be its own concept. And likely a later one. If we are going to teach type-hints then we need to enforce good ones. And that means wiring up something like |
In case you're curious, I did this by:
Kind of hacky, but it works! |
|
The def egg_count(display_value):
return len([bool(int(digit)) for digit in bin(display_value)[2:]])
print(egg_count(0b10010))
#=> 5 |
|
We can remove it. My thinking was that |
|
It was interesting to consider, but having the |
also revert most additions to `convert-to-binary-string` variation 3, as agreed upon
|
oh DUH. I am an idiot. of course it needs the if clause - we're using |
|
The other edits were really good, though! Other than that issue, I just fixed/improved a few small things. |
|
did you do the pushy-push thing? Are we ready to merge, or should we marinate it until tomm? 😄 |
If you mean force-pushing, then no, it was a normal push.
Probably one or both of us should sense-check the latest edits tomorrow with fresh eyes. |
See this issue and this forum thread.
Closes #4227 when merged.