Скачать или смотреть Why are FP devs obsessed with Referential Transparency?

Hate watching videos? Check out the complementary article, which covers the same content: https://dev.to/zelenya/why-are-fp-dev...

We clarify referential transparency, why it is so cool, what it has to do with side-effects, and what common misconceptions are. For instance, how can the code have no “side-effects”, but the program can print to the console?

💡 If you want some recaps or cheat sheets, check out these pictures:
What is Referential Transparency: https://impurepics.com/posts/2018-04-...
Referential Transparency in the Wild: https://impurepics.com/posts/2018-07-...

#fp #haskell #rust #scala

Subscribe to Impure Pics: https://bit.ly/impure-youtube

More Impure Pics
🐣   / impurepics  
📦 http://impurepics.com
👕 http://merch.impurepics.com

Functional Alphabet book
📗 Softcover: https://bit.ly/fp-abc-soft-cover
📘 Hardcover: https://bit.ly/fp-abc-hard-cover

Watch more Impure Pics
   • Debunking Haskell Myth: “Tooling Issue”  

About Impure Pics
FP Advocat. Distilling functional programming for the good of all

Get in touch: https://zelenya.com

0:00 What is Referential Transparency?
2:25 Why should I care?
4:13 What are side-effects?
5:01 RT in Rust
5:55 RT in Scala
7:52 RT in Haskell
9:19 RT trivia
10:11 Conclusion