-
Enhancement
-
Resolution: Fixed
-
P4
-
13
-
b14
See JDK-8150111.
The other bug discusses how signatures that take Iterable<Path> are problematic, because Path itself implements iterable<Path>.
This affected setLocationFromPaths and getJavaFileObjectsFromPaths. However only setLocationFromPaths was fixed in 9.
It would be nice to fix getJavaFileObjectsFromPaths too. Iterable<Path> and Collection<Path> have different erasures, so perhaps we could add getJavaFileObjectsFromPaths(Collection<Path>), deprecate getJavaFileObjectsFromPaths(Iterable<Path>), and add a default implementation that delegates to the new method.
The other bug discusses how signatures that take Iterable<Path> are problematic, because Path itself implements iterable<Path>.
This affected setLocationFromPaths and getJavaFileObjectsFromPaths. However only setLocationFromPaths was fixed in 9.
It would be nice to fix getJavaFileObjectsFromPaths too. Iterable<Path> and Collection<Path> have different erasures, so perhaps we could add getJavaFileObjectsFromPaths(Collection<Path>), deprecate getJavaFileObjectsFromPaths(Iterable<Path>), and add a default implementation that delegates to the new method.
- csr for
-
JDK-8220695 Add StandardJavaFileManager.getJavaFileObjectsFromPaths overload
-
- Closed
-