Re:Zig: a system language which prioritizes optimality, safe...
by teacup50 on Monday August 29, 2016 @04:57AM
(#12380791)
Given the litany of deprecation markers applied to existing APIs, one must presume the intention of removing them, no?
[ Parent
| on HN ]
Re:Zig: a system language which prioritizes optimality, safe...
by pcwalton on Monday August 29, 2016 @08:54AM
(#12381495)
> Given the litany of deprecation markers applied to existing APIs, one must presume the intention of removing them, no?
No! That would be a basic violation of the compatibility promise that we've upheld since 1.0.
Are you going to criticize C for marking gets() as deprecated?
Re:Zig: a system language which prioritizes optimality, safe...
by fanf2 on Tuesday August 30, 2016 @06:49AM
(#12388871)
C11 does not have gets() anymore!
Re:Zig: a system language which prioritizes optimality, safe...
by SamReidHughes on Tuesday August 30, 2016 @02:51PM
(#12392806)
Sorry, C will never live it down.
Re:Zig: a system language which prioritizes optimality, safe...
by Manishearth on Monday August 29, 2016 @08:03AM
(#12381294)
Not necessarily. I suspect even in the case of 2.0, most if not all of those apis will survive. Deprecation markers exist to encourage people to use newer, better APIs.
I suspect that even if 2.0 happened, the only apis that would be removed would be ones that we're reasonably sure nobody uses (via crater), and even then there would be debate.
And like Gankro said, 2.0 is a thing that's not supposed to happen in the first place.