IMPLICITS IN SCALA 3

on YouTube ↗29m

" summary

Scala 3 replaces the single implicit keyword with three concrete mechanisms and shows how they solve real problems: extension, using, given replace ad-hoc implicits with built‑in extension methods, explicit context parameters (multiple and anonymizable), and named or anonymous synthesizable instances. The compiler gives clearer diagnostics, givens are lazy by default, summon replaces implicit, and imports require import a.given / wildcard excludes givens so implicits no longer silently leak into scope. Examples include deriving HttpResponse[Option[T]] from HttpResponse[T].

AI-written summary · about

" chapters (15)

1. 0:00Scala 3 implicits intro
2. 1:03Scala 2 implicits flaws
3. 3:29Scala 2 implicit patterns
4. 6:21Why Scala 3 redesigned implicits
5. 8:28Scala 3’s contextual changes
6. 9:11Extension methods in Scala 3
7. 11:20Using clauses replace params
8. 13:07Clarity with using clauses
9. 17:03Given replaces implicit defs
10. 18:50Better errors with given
11. 19:54Import syntax for givens
12. 22:00Type classes in Scala 3
13. 25:14Scala 2 vs Scala 3 implicits
14. 26:58Final thoughts on Scala 3 implicits
15. 27:40Q&A

" related talks

• 29mSay goodbye to implicits - contextual abstractions in Scala 3Magda Stożek · Scala Days 2025 Lausanne
• 36mSay goodbye to implicits contextual abstractions in Scala 3Magda Stożek · ScalaCon 2022
• 42mImplicits RevisitedMartin Odersky · Lambda World Cádiz 2019
• 46mImplicits Inspected and ExplainedTim Soethout · Scala Days Berlin 2016
• 01h 04mKeynote - What to Leave ImplicitMartin Odersky · Scala Days Copenhagen 2017
• 43mDon't Fear the Implicits: Everything You Need to Know About TypeclassesDaniel Westheide · Scala Days Berlin 2016
• 30mLessons Learned from 15 Years of Scala in the WildDean Wampler · Scale By the Bay 2021
• 48mKeynote: Some Mistakes We Made When Designing ImplicitsMartin Odersky · Typelevel Summit Lausanne 2019