Yeah, whether it’s explicit method call or an implicit macro, something is being called. A constructor, a new method, that’s what I was getting at. Saying you dislike the implicit new is valid because you can’t visually see the call where in rust you can. In go, we often take the NewFactory approach even though there’s a new. It’s easier just to return the reference knowing it will out live the stack call.