Java Coding Problems

82. Avoid using var if the called names don't contain enough type information for humans

Well, var is not a silver bullet, and this problem will highlight this once again. The following snippet of code can be written using explicit types or var without losing information:

// using explicit typesMemoryCacheImageInputStream is =  new MemoryCacheImageInputStream(...);JavaCompiler jc = ToolProvider.getSystemJavaCompiler();StandardJavaFileManager fm = compiler.getStandardFileManager(...);

So, migrating the preceding snippet of code to var will result in the following code (the variables names have been chosen by visually inspecting the called names from the right-hand side):

// using varvar inputStream = new MemoryCacheImageInputStream(...);var ...