Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

“Langauges such as Rust and Go do not have this problem, mainly because they don’t have the new keyword!”

Oh but they do. You should spend some time with those languages so you can do a proper comparison.

Go has had new for a while now.



Go may (also in my understanding, it's not actually a keyword, but close enough?), but Rust does not.


Oh, excuse me, Box::new :D. At least in rust it’s an explicit method call instead of implicit.


but it's a convention right ? there's nothing special about `new` IIRC


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.


That's correct.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: