This could be the most important video I have ever watched! I know swift and have been coding with it for some time now, but this video just showed me a whole new world.
Hi Paul, I have bought a lot of your books, used them very little, I expect that to change. However you are always my goto point for knowledge on swift. Your videos are amazing!!! Sometimes I see them just for fun in stead of Netflix. Im finishing my university degree in software engineering this summer, and definitely want a job where I get to work with swift, even though the university gave no lectures on Swift. This video in particular is really good, it is enlightening to learn that you can get that much understanding from studying the sourcecode of swift. Thank you!
Amazing! I did not know that the standard library was there. I only looked into the make part of the cpp side of swift for the purpose of compiling this for illumos.
Using the de-Morgan rule for allsatisfy admittedly makes the code shorter, but a) is the Compiler smart enough to inline the inversions into the jump instructions or are they actually carried out, thereby decreasing performance? b) I guess contains is implemented the way we‘d expect? c) if so, was the choice which one to do via de-Morgan arbitrary?
Paul, thanks for sharing this knowledge. I wanted to inform you that on, 13:15 the slide does not match your voice. You say you'll add this to safer, slide shows smarter. 👋
Amazing video! Thank you Paul! The last part was a bit obscure to me. I can't understand how we go from declaring an infix operator >>> to declaring a function that is also called >>> and then use it... When we write combined = ........, we just use the infix operator, but where is our function in action? Thanks!
Coming with some OCaml, Standard ML, and Haskell experience, it's amazing how shitty some of Swift's function signatures are. First thing I noticed when he talked about *func* _&&_ . In OCaml it's just *(&&)* : _bool_ -> _bool_ -> _bool_ . I love your tutorials though, Paul. It's not your fault Swift is a shit show compared to OCaml, Standard ML, and Haskell.
This could be the most important video I have ever watched! I know swift and have been coding with it for some time now, but this video just showed me a whole new world.
I'm glad to hear you enjoyed it! I hope to be recording some new videos soon that should prove just as valuable - watch this space 👍
Like what ?
Part where you combine 3 methods was brilliant!
I nearly never comment on UA-cam videos. This is one video that I’ll make an exception for because of how great it is! Thank you for all your work.
Keep up the brilliant work! You're making a huge impact on the iOS community 🚀
Thank you for breaking everything down Paul. Thanks for all that you do for the community. Good luck with your own convention!
The composition one blew my mind 🤯 really made something click in my head. Binary relations in action!
Hi Paul, I have bought a lot of your books, used them very little, I expect that to change. However you are always my goto point for knowledge on swift. Your videos are amazing!!! Sometimes I see them just for fun in stead of Netflix. Im finishing my university degree in software engineering this summer, and definitely want a job where I get to work with swift, even though the university gave no lectures on Swift.
This video in particular is really good, it is enlightening to learn that you can get that much understanding from studying the sourcecode of swift.
Thank you!
wow, so awesome!! The rethrows one felt like magic
Just amazing
Crazy that you published it for free, many would have already put it on Udemy, and spammed sponsors or ads for the money, but you did not!
Amazing! I did not know that the standard library was there. I only looked into the make part of the cpp side of swift for the purpose of compiling this for illumos.
Such wow... I would love to see more similar videos
Using the de-Morgan rule for allsatisfy admittedly makes the code shorter, but a) is the Compiler smart enough to inline the inversions into the jump instructions or are they actually carried out, thereby decreasing performance? b) I guess contains is implemented the way we‘d expect? c) if so, was the choice which one to do via de-Morgan arbitrary?
Paul, thanks for sharing this knowledge.
I wanted to inform you that on, 13:15 the slide does not match your voice. You say you'll add this to safer, slide shows smarter. 👋
I admire you! It is really fascinating!
Ok, Paul’s a genius 🤯
Great video!
thank you, good job !
Amazing video! Thank you Paul!
The last part was a bit obscure to me.
I can't understand how we go from declaring an infix operator >>> to declaring a function that is also called >>> and then use it...
When we write combined = ........, we just use the infix operator, but where is our function in action?
Thanks!
infix operator >>> = ... is just a declaration of infix operator inside specified precedence group. Function >>> defines behavior of the operator.
Wow, this is awesome :O
Wow it's the unique lecture!
by the way why did you bring this guy? 😂 44:10
This video blow my mind
Amazing! :O
Brilliant!!!
I'm glad you enjoyed it!
Smarter, Safer, Faster
In krakow?! I used to reside there.
What terminal extensions or tools are you using?
I use zsh with Prezto: github.com/sorin-ionescu/prezto
This made me miss FSharp function compose ever more
precondition(!scores.isEmpty, "Error..") is better than precondition(scores.count > 0, "Error...") i guess )
grep "precondition(" * | wc -l
Now shows 250 :p
Boom!
🤯🤯🤯
一代新人换 mattt
Coming with some OCaml, Standard ML, and Haskell experience, it's amazing how shitty some of Swift's function signatures are. First thing I noticed when he talked about *func* _&&_ . In OCaml it's just *(&&)* : _bool_ -> _bool_ -> _bool_ . I love your tutorials though, Paul. It's not your fault Swift is a shit show compared to OCaml, Standard ML, and Haskell.