RFR 8194746: (fs) Add equivalents of Paths.get to Path interface

Roger Riggs Roger.Riggs at Oracle.com
Thu Mar 15 14:05:22 UTC 2018


Hi Alan,

Perhaps then, say it "may be deprecated"... instead of "obsolete".
or lead the api note with the recommendation to use Path.of.

Roger

On 3/15/2018 10:01 AM, Alan Bateman wrote:
>
>
> On 15/03/2018 13:54, Roger Riggs wrote:
>> Hi Brian,
>>
>> Looks fine.
>>
>> I'm not sure how to interpret "obsolete" especially in relation to 
>> the various contexts
>> where "deprecated" is used.  I think it means code that uses 
>> Paths.get should be modified
>> to use Path.of.  This sounds like a vanilla use of @deprecated with a 
>> convenient replacement.
>> Not for removal of course because there's no plan to remove it (for 
>> now).
> I don't think we should do this now as it would just annoy developers 
> that compile to multiple releases. So I think something to re-visit 
> again in a few releases.
>
> -Alan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/nio-dev/attachments/20180315/d50d0b05/attachment.html>


More information about the nio-dev mailing list