digitalmars.D - Remove "std." from library reference menu?
- Andrei Alexandrescu (8/8) Jan 24 2015 Thanks @JinShil!
- Shammah Chancellor (5/17) Jan 24 2015 Can we add an io package to std while we're at it and have std.stdio
- Dmitry Olshansky (5/21) Jan 24 2015 Please, new I/O package is in the works. Meanwhile there is no point
- weaselcat (6/14) Jan 24 2015 +1
- H. S. Teoh via Digitalmars-d (30/49) Jan 24 2015 Yeah, I think we should make std.container.* and std.range.* collapsed /
- weaselcat (2/54) Jan 24 2015 That would probably be the best solution here.
- Vladimir Panteleev (5/24) Jan 24 2015 There was a proposed change to wrap the names on the period, what
- Andrei Alexandrescu (2/4) Jan 24 2015 That's in. -- Andrei
- Vladimir Panteleev (3/8) Jan 24 2015 It doesn't seem to be working for me. (Firefox 35)
- Mike (7/16) Jan 24 2015 It works on the Pre-release pages, but not the Release pages,
- Vladimir Panteleev (3/19) Jan 24 2015 Right. And when I tested locally, I forgot to rebuild Phobos.
- H. S. Teoh via Digitalmars-d (7/12) Jan 24 2015 That's why *all* packages need to be expandable, not just the top-level
Thanks JinShil! https://github.com/D-Programming-Language/dlang.org/pull/827 The con is that some people may find it confusing, thinking they should import algorithm instead of std.algorithm etc. On the other hand the documentation of each module has "std." in clear in the heading. Thoughts? Andrei
Jan 24 2015
On 2015-01-24 17:32:15 +0000, Andrei Alexandrescu said:Thanks JinShil! https://github.com/D-Programming-Language/dlang.org/pull/827 The con is that some people may find it confusing, thinking they should import algorithm instead of std.algorithm etc. On the other hand the documentation of each module has "std." in clear in the heading. Thoughts? AndreiCan we add an io package to std while we're at it and have std.stdio public import it? :) -- -Shammah
Jan 24 2015
On 24-Jan-2015 20:43, Shammah Chancellor wrote:On 2015-01-24 17:32:15 +0000, Andrei Alexandrescu said:Please, new I/O package is in the works. Meanwhile there is no point wasting a good name for the existing ad-hoc wrapper on top of libc. -- Dmitry OlshanskyThanks JinShil! https://github.com/D-Programming-Language/dlang.org/pull/827 The con is that some people may find it confusing, thinking they should import algorithm instead of std.algorithm etc. On the other hand the documentation of each module has "std." in clear in the heading. Thoughts? AndreiCan we add an io package to std while we're at it and have std.stdio public import it? :)
Jan 24 2015
On Saturday, 24 January 2015 at 17:32:14 UTC, Andrei Alexandrescu wrote:Thanks JinShil! https://github.com/D-Programming-Language/dlang.org/pull/827 The con is that some people may find it confusing, thinking they should import algorithm instead of std.algorithm etc. On the other hand the documentation of each module has "std." in clear in the heading. Thoughts? Andrei+1 Since the fix for names leaking outside the frames, it looks bad with long std.* names wrapped. https://i.imgur.com/yhyq5pp.png
Jan 24 2015
On Sat, Jan 24, 2015 at 06:41:51PM +0000, weaselcat via Digitalmars-d wrote:On Saturday, 24 January 2015 at 17:32:14 UTC, Andrei Alexandrescu wrote:Yeah, I think we should make std.container.* and std.range.* collapsed / expandable as well. It should look something like this: std » algorithm ... » (+) container » conv » csv ... When expanded it should look something like this: std » algorithm ... » (-) container » binaryheap » dlist » rbtree » slist » util » conv » csv ... Not sure about the exact location of the expand button, but you get the idea. T -- It is of the new things that men tire --- of fashions and proposals and improvements and change. It is the old things that startle and intoxicate. It is the old things that are young. -- G.K. ChestertonThanks JinShil! https://github.com/D-Programming-Language/dlang.org/pull/827 The con is that some people may find it confusing, thinking they should import algorithm instead of std.algorithm etc. On the other hand the documentation of each module has "std." in clear in the heading. Thoughts? Andrei+1 Since the fix for names leaking outside the frames, it looks bad with long std.* names wrapped. https://i.imgur.com/yhyq5pp.png
Jan 24 2015
On Saturday, 24 January 2015 at 18:50:12 UTC, H. S. Teoh wrote:On Sat, Jan 24, 2015 at 06:41:51PM +0000, weaselcat via Digitalmars-d wrote:That would probably be the best solution here.On Saturday, 24 January 2015 at 17:32:14 UTC, Andrei Alexandrescu wrote:Yeah, I think we should make std.container.* and std.range.* collapsed / expandable as well. It should look something like this: std » algorithm ... » (+) container » conv » csv ... When expanded it should look something like this: std » algorithm ... » (-) container » binaryheap » dlist » rbtree » slist » util » conv » csv ... Not sure about the exact location of the expand button, but you get the idea. TThanks JinShil! https://github.com/D-Programming-Language/dlang.org/pull/827 The con is that some people may find it confusing, thinking they should import algorithm instead of std.algorithm etc. On the other hand the documentation of each module has "std." in clear in the heading. Thoughts? Andrei+1 Since the fix for names leaking outside the frames, it looks bad with long std.* names wrapped. https://i.imgur.com/yhyq5pp.png
Jan 24 2015
On Saturday, 24 January 2015 at 18:41:52 UTC, weaselcat wrote:On Saturday, 24 January 2015 at 17:32:14 UTC, Andrei Alexandrescu wrote:There was a proposed change to wrap the names on the period, what happened to that? I'm worried that this is an interim solution that only buys a little time until we put more things into packages.Thanks JinShil! https://github.com/D-Programming-Language/dlang.org/pull/827 The con is that some people may find it confusing, thinking they should import algorithm instead of std.algorithm etc. On the other hand the documentation of each module has "std." in clear in the heading. Thoughts? Andrei+1 Since the fix for names leaking outside the frames, it looks bad with long std.* names wrapped. https://i.imgur.com/yhyq5pp.png
Jan 24 2015
On 1/24/15 10:50 AM, Vladimir Panteleev wrote:There was a proposed change to wrap the names on the period, what happened to that?That's in. -- Andrei
Jan 24 2015
On Saturday, 24 January 2015 at 18:55:28 UTC, Andrei Alexandrescu wrote:On 1/24/15 10:50 AM, Vladimir Panteleev wrote:It doesn't seem to be working for me. (Firefox 35)There was a proposed change to wrap the names on the period, what happened to that?That's in. -- Andrei
Jan 24 2015
On Sunday, 25 January 2015 at 01:41:15 UTC, Vladimir Panteleev wrote:On Saturday, 24 January 2015 at 18:55:28 UTC, Andrei Alexandrescu wrote:It works on the Pre-release pages, but not the Release pages, right? You pulled the fix (https://github.com/D-Programming-Language/dlang.org/commit/2ce7126ef103c4de0c4c84 16798ae3ea20aac34), but it looks like it hasn't been published yet. MikeOn 1/24/15 10:50 AM, Vladimir Panteleev wrote:It doesn't seem to be working for me. (Firefox 35)There was a proposed change to wrap the names on the period, what happened to that?That's in. -- Andrei
Jan 24 2015
On Sunday, 25 January 2015 at 01:48:50 UTC, Mike wrote:On Sunday, 25 January 2015 at 01:41:15 UTC, Vladimir Panteleev wrote:Right. And when I tested locally, I forgot to rebuild Phobos. Thanks :)On Saturday, 24 January 2015 at 18:55:28 UTC, Andrei Alexandrescu wrote:It works on the Pre-release pages, but not the Release pages, right? You pulled the fix (https://github.com/D-Programming-Language/dlang.org/commit/2ce7126ef103c4de0c4c84 16798ae3ea20aac34), but it looks like it hasn't been published yet.On 1/24/15 10:50 AM, Vladimir Panteleev wrote:It doesn't seem to be working for me. (Firefox 35)There was a proposed change to wrap the names on the period, what happened to that?That's in. -- Andrei
Jan 24 2015
On Sat, Jan 24, 2015 at 06:50:17PM +0000, Vladimir Panteleev via Digitalmars-d wrote: [...]There was a proposed change to wrap the names on the period, what happened to that? I'm worried that this is an interim solution that only buys a little time until we put more things into packages.That's why *all* packages need to be expandable, not just the top-level std. T -- Let's not fight disease by killing the patient. -- Sean 'Shaleh' Perry
Jan 24 2015