Raw String Literals Removed From Java 12 as Feature Set Frozen

Re:Raw String Literals Removed From Java 12 as Feature Set F... by idontpost on Saturday December 22, 2018 @02:50PM (#18742127)

> If imports are renamed, you would have to actually care about the import statements.

Not really. VS Code transparently handles aliasing of imports in JS. You still never need to look at them manually AND you get the benefit of cleaner naming.

[ Parent | on HN ]

Re:Raw String Literals Removed From Java 12 as Feature Set F... by halfastack on Sunday December 23, 2018 @01:41AM (#18744801)

I have difficulty seeing what this would add. As a Java developer, I know what "List" is, just like I know what "ArrayList" is. If someone instantiated new better.ArrayList(), I immediately have to check what the hell is the import (go to the top of the class, uncollapse the import statements, and see what is "better").

As with all code readability, I assume to write and use import aliases, that's very easy. The person who's gonna read it after you, they've got a problem. And that's why I'd personally be strongly against this in my code review.

[ Parent | on HN ]

Re:Raw String Literals Removed From Java 12 as Feature Set F... by idontpost on Sunday December 23, 2018 @05:17PM (#18748720)

Using the example from your other reply:

import java.awt.List as awtList

import java.util.List as utilList

Granted, there's not a lot of scenarios where you have this sort of collision, but it does happen and using aliasing makes the code easier to read.

[ Parent | on HN ]

Re:Raw String Literals Removed From Java 12 as Feature Set F... by ptx on Sunday December 23, 2018 @05:15AM (#18745365)

> As a Java developer, I know what "List" is

Is that java.awt.List or java.util.List?

[ Parent | on HN ]