Re: What's up with ddoc on dlang.org?
On 04/02/2018 06:13 PM, ag0aep6g wrote: On 04/02/2018 11:36 PM, Steven Schveighoffer wrote: Was just perusing dlang's library documentation, and here is the description it has for std.experimental.allocator.make: Dynamically allocates (using ) and then creates in the memory allocated an object of type T, using (if any) for its initialization. Initialization occurs in the memory allocated and is otherwise semantically the same as T(). (Note that using .!(T[]) creates a pointer to an (empty) array of Ts, not an array. To use an allocator to allocate and initialize an array, use .makeArray!T described below.) Seems there's a few things missing here? What's happening? Looks like a mistake that happened with this change: https://dlang.org/changelog/2.079.0.html#fix18361 PR to fix it: https://github.com/dlang/dlang.org/pull/2326 Thanks, I'd just found that too.
Re: What's up with ddoc on dlang.org?
On Monday, 2 April 2018 at 21:36:33 UTC, Steven Schveighoffer wrote: Was just perusing dlang's library documentation, and here is the description it has for std.experimental.allocator.make: Dynamically allocates (using ) and then creates in the memory allocated an object of type T, using (if any) for its initialization. Initialization occurs in the memory allocated and is otherwise semantically the same as T(). (Note that using .!(T[]) creates a pointer to an (empty) array of Ts, not an array. To use an allocator to allocate and initialize an array, use .makeArray!T described below.) Seems there's a few things missing here? What's happening? -Steve I assume this is due the fact that we disabled Ddoc' infamous auto-highlighting recently: https://github.com/dlang/dlang.org/pull/2307 However, I will have a look, but I saw a lot of -> path replacements in: https://github.com/dlang/phobos/pull/6391 So this might have been fixed partially already.
Re: What's up with ddoc on dlang.org?
On 04/02/2018 11:36 PM, Steven Schveighoffer wrote: Was just perusing dlang's library documentation, and here is the description it has for std.experimental.allocator.make: Dynamically allocates (using ) and then creates in the memory allocated an object of type T, using (if any) for its initialization. Initialization occurs in the memory allocated and is otherwise semantically the same as T(). (Note that using .!(T[]) creates a pointer to an (empty) array of Ts, not an array. To use an allocator to allocate and initialize an array, use .makeArray!T described below.) Seems there's a few things missing here? What's happening? Looks like a mistake that happened with this change: https://dlang.org/changelog/2.079.0.html#fix18361 PR to fix it: https://github.com/dlang/dlang.org/pull/2326
What's up with ddoc on dlang.org?
Was just perusing dlang's library documentation, and here is the description it has for std.experimental.allocator.make: Dynamically allocates (using ) and then creates in the memory allocated an object of type T, using (if any) for its initialization. Initialization occurs in the memory allocated and is otherwise semantically the same as T(). (Note that using .!(T[]) creates a pointer to an (empty) array of Ts, not an array. To use an allocator to allocate and initialize an array, use .makeArray!T described below.) Seems there's a few things missing here? What's happening? -Steve
