News for hackers. Stuff that matters.

A comment on C++26: A Placeholder with No Name. Parent comment

Re:C++26: A Placeholder with No Name by Too on Saturday January 11, 2025 @08:22AM (#42665683)
Every other language does that by default with "var", "let", or in some languages nothing at all. Within functions it doesn't matter that much and using an IDE takes care of quick lookups anyway.
[ Parent | on HN ]
Re:C++26: A Placeholder with No Name by dgfitz on Saturday January 11, 2025 @12:30PM (#42667382)
Wasn’t typescript created to fix this problem for JS?
[ Parent | on HN ]
Re:C++26: A Placeholder with No Name by jeremyjh on Saturday January 11, 2025 @02:54PM (#42668492)
Using `let` does not make the expression un-typed in Typescript. It means the type is inferred, and you'll get type warnings if you use it where a different type is expected.
[ Parent | on HN ]
Re:C++26: A Placeholder with No Name by maccard on Saturday January 11, 2025 @12:51PM (#42667558)
Even for the non ide folks - vim emacs and vs code all have excellent support for that.
[ Parent | on HN ]
Re:C++26: A Placeholder with No Name by ranger_danger on Saturday January 11, 2025 @01:20PM (#42667813)
How does vim support this? I thought you had to use custom scripts/extensions to do it?
[ Parent | on HN ]
Re:C++26: A Placeholder with No Name by maccard on Saturday January 11, 2025 @02:31PM (#42668328)
Sorry I wasn’t clear - all those editors have simple (ish) plugins that support it
[ Parent | on HN ]