mCoding

Functions within functions explained!

― mCoding with James Murphy (https://mcoding.io)

Source code: https://github.com/mCodingLLC/VideosSampleCode

SUPPORT ME ⭐
---------------------------------------------------
Sign up on Patreon to get your donor role and early access to videos!
https://patreon.com/mCoding

Feeling generous but don't have a Patreon? Donate via PayPal! (No sign up needed.)
https://www.paypal.com/donate/?hosted_button_id=VJY5SLZ8BJHEE

Want to donate crypto? Check out the rest of my supported donations on my website!
https://mcoding.io/donate

Top patrons and donors: Jameson, Laura M, Dragos C, Vahnekie, Neel R, Matt R, Johan A, Casey G, John Martin, Mutual Information


BE ACTIVE IN MY COMMUNITY 😄
---------------------------------------------------
Discord: https://discord.gg/Ye9yJtZQuN
Github: https://github.com/mCodingLLC/
Reddit: https://www.reddit.com/r/mCoding/
Facebook: https://www.facebook.com/james.mcoding

CHAPTERS
---------------------------------------------------
0:00 Intro
0:18 Motivating example
2:54 The One Rule
3:13 Level 1, return global
3:38 Level 2, conditional local
4:50 Level 3, nonlocal z
6:48 Level 4, cells and closures
10:35 Level 5, functions are objects, distinct closures
11:39 Level 6, donky chonky
12:52 Lambdas and comprehensions
14:32 Nonlocal and global
16:27 Level 7, please dont do this
18:18 Thanks

Functions within functions, closures, and variable scopes in Python

Guido van Rossum said he would have never put this into Python.

If he had to make Python again, he would have never put for/else and while/else into the language. Why would a potentially useful feature that saves extra variables be seen as such a mistake? Find out in this video, where we see how for/else while/else work, where they came from, and why you should probably avoid them in your own professional Python code.

― mCoding with James Murphy (https://mcoding.io)

Source code: https://github.com/mCodingLLC/VideosSampleCode
Create custom lint rules: https://youtu.be/OjPT15y2EpE
Guido's 2009 opinion: https://mail.python.org/pipermail/python-ideas/2009-October/006157.html

SUPPORT ME ⭐
---------------------------------------------------
Patreon: https://patreon.com/mCoding
Paypal: https://www.paypal.com/donate/?hosted_button_id=VJY5SLZ8BJHEE
Other donations: https://mcoding.io/donate

Top patrons and donors: Jameson, Laura M, Vahnekie, Dragos C, Matt R, Casey G, Johan A, John Martin, Jason F, Mutual Information, Neel R

BE ACTIVE IN MY COMMUNITY 😄
---------------------------------------------------
Discord: https://discord.gg/Ye9yJtZQuN
Github: https://github.com/mCodingLLC/
Reddit: https://www.reddit.com/r/mCoding/
Facebook: https://www.facebook.com/james.mcoding

Python's creator wishes this feature never existed

It's true, so why so many wrong proofs?

There are many incorrect proofs that .999... = 1 on YouTube and elsewhere. In this video we see why all those proofs are wrong, and then demystify what is actually meant when a mathematician says .999... = 1 and I explain why it is actually true. Did your favorite math creator make one of these mistakes?

*Title only applies before the first viewing of this video and only to people who have not studied real analysis.

― mCoding with James Murphy (https://mcoding.io)

References on the standard definition of decimals and repeating decimals (please read if you are confused or unsure about the standard notation):
https://www.math.utah.edu/~bertram/courses/4030/Reals.pdf
https://people.math.sc.edu/filaseta/gradcourses/Math785/Math785Notes1.pdf
https://www.ndsu.edu/pubweb/~comez/Decimal%20expansion.pdf
http://kevincarmody.com/math/repeatingdecimals.pdf
https://amsi.org.au/teacher_modules/pdfs/Real_numbers.pdf

SUPPORT ME ⭐
---------------------------------------------------
Patreon: https://patreon.com/mCoding
Paypal: https://www.paypal.com/donate/?hosted_button_id=VJY5SLZ8BJHEE
Other donations: https://mcoding.io/donate

BE ACTIVE IN MY COMMUNITY 😄
---------------------------------------------------
Discord: https://discord.gg/Ye9yJtZQuN
Github: https://github.com/mCodingLLC/
Reddit: https://www.reddit.com/r/mCoding/
Facebook: https://www.facebook.com/james.mcoding

Every PROOF you've seen that .999... = 1 is WRONG

What's faster, a for loop, a while loop, or something else?

We try several different ways to accomplish a looping task and discover which is fastest.

― mCoding with James Murphy (https://mcoding.io)

Source code: https://github.com/mCodingLLC/VideosSampleCode

SUPPORT ME ⭐
---------------------------------------------------
Patreon: https://patreon.com/mCoding
Paypal: https://www.paypal.com/donate/?hosted_button_id=VJY5SLZ8BJHEE
Other donations: https://mcoding.io/donate

BE ACTIVE IN MY COMMUNITY 😄
---------------------------------------------------
Discord: https://discord.gg/Ye9yJtZQuN
Github: https://github.com/mCodingLLC/
Reddit: https://www.reddit.com/r/mCoding/
Facebook: https://www.facebook.com/james.mcoding

The Fastest Way to Loop in Python - An Unfortunate Truth

Don't fall for it!

The Zen of Python must not have been invented yet because this feature is confusing, not obvious, implicit, and much more. Private name mangling in Python converts variable usages like __var into _ClassName__var at compile time and there's no warning it's happening until you run into the trap.

― mCoding with James Murphy (https://mcoding.io)

Source code: https://github.com/mCodingLLC/VideosSampleCode
Python docs: https://docs.python.org/3/tutorial/classes.html?highlight=private#private-variables
CPython mangle: https://github.com/python/cpython/blob/ab02262cd0385a2fb5eb8a6ee3cedd4b4bb969f3/Python/compile.c#L542

SUPPORT ME ⭐
---------------------------------------------------
Sign up on Patreon to get your donor role and early access to videos!
https://patreon.com/mCoding

Feeling generous but don't have a Patreon? Donate via PayPal! (No sign up needed.)
https://www.paypal.com/donate/?hosted_button_id=VJY5SLZ8BJHEE

Want to donate crypto? Check out the rest of my supported donations on my website!
https://mcoding.io/donate

Top patrons and donors: Jameson, Laura M, Dragos C, Vahnekie, Neel R, Matt R, Johan A, Casey G, Mark M, Mutual Information

BE ACTIVE IN MY COMMUNITY 😄
---------------------------------------------------
Discord: https://discord.gg/Ye9yJtZQuN
Github: https://github.com/mCodingLLC/
Reddit: https://www.reddit.com/r/mCoding/
Facebook: https://www.facebook.com/james.mcoding

CHAPTERS
---------------------------------------------------
0:00 Unexpected output
2:31 Private name mangling
4:23 Python does not have private variables
4:54 Mangling rules
6:51 Mangling at compile time
8:28 Compiler explorer
10:18 getattr and setattr
10:55 To mangle or not to mangle?
13:53 Thanks

Every Python dev falls for this (name mangling)

If you thought x+=y means x=x+y you'd be wrong!

Python's plus equals augmented assignment syntax is more complex than many people realize. Let's take a look.

(Sorry for the dark purple again! I've changed it in my ide to pink for the future!)

― mCoding with James Murphy (https://mcoding.io)

Source code: https://github.com/mCodingLLC/VideosSampleCode
Docs for iadd: https://docs.python.org/3/reference/datamodel.html#object.__iadd__

SUPPORT ME ⭐
---------------------------------------------------
Patreon: https://patreon.com/mCoding
Paypal: https://www.paypal.com/donate/?hosted_button_id=VJY5SLZ8BJHEE
Other donations: https://mcoding.io/donate

BE ACTIVE IN MY COMMUNITY 😄
---------------------------------------------------
Discord: https://discord.gg/Ye9yJtZQuN
Github: https://github.com/mCodingLLC/
Reddit: https://www.reddit.com/r/mCoding/
Facebook: https://www.facebook.com/james.mcoding

Python's sharpest corner is ... plus equals? (+=)

How many nooby C++ habits do you have?

Up your C++ skill by recognizing and ditching these nooby C++ habits. Post how many you fell for!

― mCoding with James Murphy (https://mcoding.io)

Source code: https://github.com/mCodingLLC/VideosSampleCode
C++ Core Guidelines: https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines

SUPPORT ME ⭐
---------------------------------------------------
Patreon: https://patreon.com/mCoding
Paypal: https://www.paypal.com/donate/?hosted_button_id=VJY5SLZ8BJHEE
Other donations: https://mcoding.io/donate

Top patrons and donors: Jameson, Laura M, Dragos C, Vahnekie, John Martin, Casey G, Pieter G, Krisztian M,  Mutual Information, Sigmanificient

BE ACTIVE IN MY COMMUNITY 😄
---------------------------------------------------
Discord: https://discord.gg/Ye9yJtZQuN
Github: https://github.com/mCodingLLC/
Reddit: https://www.reddit.com/r/mCoding/
Facebook: https://www.facebook.com/james.mcoding

CHAPTERS
---------------------------------------------------
0:00 Intro
0:13 #1. using namespace std
0:42 #2. using std endl in a loop
0:55 #3. index based for when range-for fits better
1:10 #4. rewriting std algorithms
1:34 #5. using C array over std array
1:50 #6. any use of reinterpret cast
2:39 #7. casting away const
3:24 #8. not knowing map bracket inserts element
3:39 #9. ignoring const-correctness
3:59 #10. not knowing string literal lifetime
4:12 #11. not using structured bindings
4:47 #12. out-params instead of returning a struct
5:04 #13. not using constexpr
5:21 #14. forgetting to mark destructor virtual
6:10 #15. thinking class members init in order of init list
6:37 #16. not knowing about default vs value initialization
7:28 #17. MAGIC NUMBERS
7:41 #18. modifying a container while looping over it
8:30 #19. returning std move of a local
9:10 #20. thinking std move moves something
9:42 #21. thinking evaluation order is left to right
10:56 #22. unnecessary heap allocations
11:23 #23. not using unique ptr and shared ptr
12:11 #24. not using make unique and make shared
12:23 #25. any use of new and delete
12:52 #26. any manual resource management
13:24 #27. thinking raw pointers are bad
14:25 #28. using shared ptr when unique ptr would do
14:48 #29. thinking shared ptr is thread-safe
15:26 #30. mixing up const ptr vs ptr to const
16:00 #31. ignoring compiler warnings

31 nooby C++ habits you need to ditch

Embrace the copy-free lifestyle!

― mCoding with James Murphy (https://mcoding.io)

Source code: https://github.com/mCodingLLC/VideosSampleCode
Cppref on copy elision: https://en.cppreference.com/w/cpp/language/copy_elision

SUPPORT ME ⭐
---------------------------------------------------
Sign up on Patreon to get your donor role and early access to videos!
https://patreon.com/mCoding

Feeling generous but don't have a Patreon? Donate via PayPal! (No sign up needed.)
https://www.paypal.com/donate/?hosted_button_id=VJY5SLZ8BJHEE

Want to donate crypto? Check out the rest of my supported donations on my website!
https://mcoding.io/donate

Top patrons and donors: Jameson, Laura M, Dragos C, Vahnekie, Neel R, Matt R, Johan A, Casey G, John Martin, Mutual Information

BE ACTIVE IN MY COMMUNITY 😄
---------------------------------------------------
Discord: https://discord.gg/Ye9yJtZQuN
Github: https://github.com/mCodingLLC/
Reddit: https://www.reddit.com/r/mCoding/
Facebook: https://www.facebook.com/james.mcoding

CHAPTERS
---------------------------------------------------
0:00 Intro
0:40 Return Value Optimization
3:06 Where do the copies come from?
5:23 When can copies be elided?
7:46 C++17 mandatory copy elision
9:38 Thanks