I was wondering if it’d make sense to have some kind of default instance of ActorMaterializer accessible from an ActorSystem. It might become handy to access it from the implicitly passed ActorSystem rather than implicitly pass both ActorMaterializer as well the ActorSystem or always create a new ActorMaterilizer (which is not recommended).
This one is also somewhat related, but the other way around, so to speak, accessing the actor system from custom graph stages: https://github.com/akka/akka/issues/26192