This just in! When is a constructor that returns an interface appropriate? 🤔
Update: 2024-05-17
Description
- Upcoming conferences
- 🇯🇵 June 8: Go Conference 2024 @ Tokyo, Japan
- 🇩🇪 June 17-20: GopherCon EU @ Berlin, Germany
- 🇳🇱 June 19-21: DevOps Days @ Amsterdam, Netherlands
- 🇷🇺 June 24-25: Golang Conf 2024 @ St. Petersburg, Russia
- Proposals
- 👍 Accepted: go telemetry subcommand
- Previous discussion on Episode 62
- ⛔ Declined: Notify of new major dependency versions
- Previous discussion on Episode 62
- 🆕 New: Make math/rand.Seed a no-op
- 👍 Accepted: go telemetry subcommand
- The unique package has been implemented
- ✅ Previous discussion on Episode 33
- Around the community
- 🤔 Reddit: Is it idiomatic to create a constructor that returns an interface?
- GitHub CLI 2.49.1 includes contribution from Shay
In Channel
Download from Google Play
Download from App Store
United States00:00
00:00
x
"Depend on abstraction, pass realization" is letter "D" in SOLID principles - dependency inversion principle. You should know what it means, don't you? )
There is no point in creating the interface in tests since all the places you are going to pass data will accept your struct.