> So personally I have tried it with the projects we work on(large, heavily templated C++ projects) and issues I have is that using auto confuses the hell out o

> So personally I have tried it with the projects we work on(large, heavily templated C++ projects) and issues I have is that using auto confuses the hell out of VisualAssist and Intellisense(80% of the time they just can't guess what the type actually is) that's a problem with your IDE, I use QtCreator which leverages clang for parsing and gets it right the immense majority of time in my experience. > but the worst part is that the debugger doesn't know either - so any time I get a crash with auto I need to spend additional few minutes to find the actual type(and the right template!) and cast it manually in the watch window, this sounds like a deeper bug with VS. I use debugging with cdb, windbg, and VS IDE, and the debugger never had trouble with "auto" variables - I don't understand why it would, since in the binary debug info it's the actual type which is saved. Did you report it to MS ? I don't know how large is your project, the main one I'm working on is overall a bit more than 300kloc and VS2017 had no problems with it last time I had to use it for reference.