"Composition over inheritance" is not a new trend, that was actually mentioned in first chapter of Gang of four's Design Patterns in 1995 [1]. In that regard, I feel like we mostly failed to ever use OOP properly (although, "fail" is probably too strong a word).
I'm actually annoyed that embedded types exist in go because it re-introduces the same problem (but I have an easy fix for that: I don't use them).
But really, what you're describing is a data structure problem. This can be solved without OOP, and structs are especially good at it.
[1] https://en.wikipedia.org/wiki/Design_Patterns#Introduction.2...