Skip to content
Hallway
0:00 / 0:00

#scala3#composition#exports

Favor composition over inheritance in #Scala3 with exports!

DevInsideYou

13K subscribers • 47 videos on Hallway

YouTube
  • Recommended by 1 person: 1 in engineering communities.
  • Linked in the descriptionlampepfl/dotty
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

1.4K views5 years ago1 recommendation

Programming languagesSoftware designScalaDesign patternsObject-oriented design

How to reduce boilerplate when favoring composition over inheritance by using the export feature in Scala 3.

In this video we are going to see how some boilerplate associated with composition can be reduced in Scala3. Export Java Symbols compiles, but fails at runtime with NoClassDefFoundError. github.com/lampepfl/dotty/issues/12249 Table of Contents: Intro Setup Boundary, Google, Storage EntityGateway GoogleImpl and StorageImpl DependencyGraph Test The Problem The Solution(s) A trick! A bug or a limitation, but definitely not a feature! Conclusion Website: devinsideyou.com Patreon: patreon.devinsideyou.com Discord: discord.devinsideyou.com Telegram: telegram.devinsideyou.com Twitter: twitter.devinsideyou.com GitHub: github.devinsideyou.com LBRY: lbry.devinsideyou.com Install scripts: install.devinsideyou.com Giter8 templates: g8.devinsideyou.com Spotify concentration playlist: code.radio.devinsideyou.com Cheers and Happy Coding! #scala #tutorial #programming

Why it's here

1 person recommends this

What people say. Recommended for demonstrating how Scala 3 exports make composition easier and cleaner than inheritance.

u/agilesteelin r/scala • Recommends

Favor composition over inheritance in Scala3 with exports!
31View on Reddit