• Chris (10/10) Apr 27 2016 Something I've wanted to ask for a while: Would it be possible to
• rikki cattermole (2/11) Apr 27 2016 Alternatively we could also just keep older versions of Phobos docs arou...
• Chris (9/11) Apr 27 2016 That would be ok too, although I like the idea of having info
• Jacob Carlborg (5/8) Apr 27 2016 In Swift they even added language support for using different versions
• Chris (9/18) Jun 30 2016 I've just had the case where LDC (based on 2.070.2) did not
• Chris (4/12) Jun 30 2016 LDC is apparently in sync now:

Chris <wendlec tcd.ie> writes:

Something I've wanted to ask for a while: Would it be possible to 
add version info to the library reference (henceforth)? In 
Apple's Cocoa API reference they always say since `10.8` etc. 
which used to be very helpful.

The reason I'm asking is that I'm usually stuck with an older 
version of dmd (1 or 2 releases behind) and only once I've 
finished debugging/enhancing can I move on to the current version 
and update my code base, cos sometimes vibed is not yet 
compatible with the latest version(s) of D and/or I want to be 
able to compile release versions with LDC.

rikki cattermole <rikki cattermole.co.nz> writes:

On 27/04/2016 9:14 PM, Chris wrote:
 Something I've wanted to ask for a while: Would it be possible to add
 version info to the library reference (henceforth)? In Apple's Cocoa API
 reference they always say since `10.8` etc. which used to be very helpful.

 The reason I'm asking is that I'm usually stuck with an older version of
 dmd (1 or 2 releases behind) and only once I've finished
 debugging/enhancing can I move on to the current version and update my
 code base, cos sometimes vibed is not yet compatible with the latest
 version(s) of D and/or I want to be able to compile release versions
 with LDC.

Alternatively we could also just keep older versions of Phobos docs around.

Chris <wendlec tcd.ie> writes:

On Wednesday, 27 April 2016 at 09:19:33 UTC, rikki cattermole 
wrote:
 Alternatively we could also just keep older versions of Phobos 
 docs around.

That would be ok too, although I like the idea of having info 
about when something was added. It's nice to see the progress of 
the library and it's more economical. You can go to the current 
docs and only go back to an older version, if you have to. Most 
of the time, it will be the same anyway. Plus (which is very 
important): it highlights new features you might otherwise have 
overlooked, so you can make a mental note.

Jacob Carlborg <doob me.com> writes:

On 2016-04-27 11:14, Chris wrote:
 Something I've wanted to ask for a while: Would it be possible to add
 version info to the library reference (henceforth)? In Apple's Cocoa API
 reference they always say since `10.8` etc. which used to be very helpful.

In Swift they even added language support for using different versions 
of the API's.

-- 
/Jacob Carlborg

Chris <wendlec tcd.ie> writes:

On Wednesday, 27 April 2016 at 12:47:01 UTC, Jacob Carlborg wrote:
 On 2016-04-27 11:14, Chris wrote:
 Something I've wanted to ask for a while: Would it be possible 
 to add
 version info to the library reference (henceforth)? In Apple's 
 Cocoa API
 reference they always say since `10.8` etc. which used to be 
 very helpful.

 In Swift they even added language support for using different 
 versions of the API's.

I've just had the case where LDC (based on 2.070.2) did not 
compile code based on Phobos 2.071.1, which is nothing unusual of 
course. Only it would have been nice, if the function 
`std.algorithm.maxPos` had had the info "since 2.071.0" attached 
to it. How am I supposed to know that `maxPos` is new while 
`minPos` was already available in 2.070.0. It'd make things a bit 
smoother, especially because not all compilers use the same 
version of Phobos.

Chris <wendlec tcd.ie> writes:

On Thursday, 30 June 2016 at 15:47:52 UTC, Chris wrote:
 I've just had the case where LDC (based on 2.070.2) did not 
 compile code based on Phobos 2.071.1, which is nothing unusual 
 of course. Only it would have been nice, if the function 
 `std.algorithm.maxPos` had had the info "since 2.071.0" 
 attached to it. How am I supposed to know that `maxPos` is new 
 while `minPos` was already available in 2.070.0. It'd make 
 things a bit smoother, especially because not all compilers use 
 the same version of Phobos.

LDC is apparently in sync now:

http://forum.dlang.org/post/czukvcubxxuskbknkcnr forum.dlang.org

But still, version info in the library would be veeeery nice.