Am 22.12.2012 00:46, schrieb Andrei Alexandrescu:
* But by very, very far the community-contributed stuff is just perfect. I
really really really hope
we can get something like that integrated. There are many ways to approach
this:
- By integrating a wiki page via e.g. an IFRAME.
- By
On 12/25/2012 08:17 PM, Sönke Ludwig wrote:
e.g.
http://vibed.org/temp/d-programming-language.org/phobos/std/algorithm/balancedParens.html
Looks good!
BTW the link
http://vibed.org/temp/d-programming-language.org/phobos/std/algorithm/boyerMooreFinder.html
gives a 404 error (linked from
On 2012-12-23 20:55, Sönke Ludwig wrote:
I changed the first column from width: 150pt; to min-width: 170pt. It can
still wrap, but the
two columns can now freely fight for the space if they need to.
Looks much better, thanks.
--
/Jacob Carlborg
On Sunday, 23 December 2012 at 07:38:04 UTC, Sönke Ludwig wrote:
What I did now was to hide the manually written Source:
section (which is not in every module) and
instead generate a procedural View source code button on the
top right of the page (which should
always be there).
So if you have
Am 23.12.2012 10:11, schrieb Rob T:
On Sunday, 23 December 2012 at 07:38:04 UTC, Sönke Ludwig wrote:
What I did now was to hide the manually written Source: section (which is
not in every module) and
instead generate a procedural View source code button on the top right of
the page (which
On 12/22/2012 9:36 AM, Andrei Alexandrescu wrote:
Good idea. I'm a big fan of moving uninteresting stuff off the top of a page.
Maybe the source does carry some interest though.
More creative ideas is to represent all that information not in normal paragraph
style, but as small print in a band
Am 23.12.2012 10:55, schrieb Philippe Sigaud:
Very nice-looking docs Sönke!
A minor nitpick: in some modules, the _-prefixed version appears as such (I
mean, with an underscore
before the name). See for example:
On Saturday, 22 December 2012 at 23:04:47 UTC, Andrei
Alexandrescu wrote:
On 12/22/12 5:10 PM, foobar wrote:
On Friday, 21 December 2012 at 21:58:34 UTC, Jacob Carlborg
wrote:
On 2012-12-21 18:05, Andrei Alexandrescu wrote:
s/remove/integrate/
s/ugly/awesome/
It's ugly that they are
On 12/23/12 6:44 AM, foobar wrote:
Using an all encompassing algorithms module is also unhelpful as all
code is essentially an algorithm to accomplish some task. This is akin
to opening a store called - A store or perhaps A place to sell you
stuff.
That I disagree with a bit. I think it's
On 2012-12-22 18:53, Sönke Ludwig wrote:
- jumps to line numbers on github (which are off because of changes after the
release)
Can you lock it to the same hash that the docs are generated from?
--
/Jacob Carlborg
On 2012-12-22 18:53, Sönke Ludwig wrote:
In the latest upload a number of items is addressed:
- vertical margins at the top
- redundant column headers
- +/- signs for the package tree
- jumps to line numbers on github (which are off because of changes after the
release)
- some macro
On 2012-12-22 17:15, Andrei Alexandrescu wrote:
Looks great! I think that belongs in an index page (which doesn't exist
yet, though we do define a sitemap http://dlang.org/sitemap.html).
The sitemap is a bit different. The list of symbols could be the index
page or a part of the index page
On Sunday, 23 December 2012 at 13:21:16 UTC, Andrei Alexandrescu
wrote:
On 12/23/12 6:44 AM, foobar wrote:
Using an all encompassing algorithms module is also
unhelpful as all
code is essentially an algorithm to accomplish some task. This
is akin
to opening a store called - A store or perhaps
On 12/23/12 9:08 AM, foobar wrote:
Regarding std.algorithm, the module isn't called - 'classic, consecrated
algorithms the kind you'll find in a book entitled Algorithms'. It is
simply called 'std.algorithm' and there are many, *many* books on
algorithms. Should this module include concurrent
On Sunday, 23 December 2012 at 14:43:25 UTC, Andrei Alexandrescu
wrote:
On 12/23/12 9:08 AM, foobar wrote:
Regarding std.algorithm, the module isn't called - 'classic,
consecrated
algorithms the kind you'll find in a book entitled
Algorithms'. It is
simply called 'std.algorithm' and there are
On Sunday, 23 December 2012 at 16:06:57 UTC, John Colvin wrote:
On Sunday, 23 December 2012 at 14:43:25 UTC, Andrei
Alexandrescu wrote:
I like std.algorithm the way it is.
Andrei
Same here. In my mind it's about generality:
General purpose algorithms (sort, partition etc.) belong in
On 12/23/12 12:54 PM, Peter Alexander wrote:
On Sunday, 23 December 2012 at 16:06:57 UTC, John Colvin wrote:
On Sunday, 23 December 2012 at 14:43:25 UTC, Andrei Alexandrescu wrote:
I like std.algorithm the way it is.
Andrei
Same here. In my mind it's about generality:
General purpose
Am 23.12.2012 14:52, schrieb Jacob Carlborg:
On 2012-12-22 18:53, Sönke Ludwig wrote:
- jumps to line numbers on github (which are off because of changes after
the release)
Can you lock it to the same hash that the docs are generated from?
I've locked it to the v2.060 tag now, but as
On Sunday, December 23, 2012 18:54:15 Peter Alexander wrote:
Would it be possible to split the library up and add public
imports to std.algorithm of the moved symbols?
DIPs 15 and 16 relate to the ability to split up a module into separate
modules within a package with the same name without
Am 23.12.2012 14:58, schrieb Jacob Carlborg:
I think it would be better if there was more space for the Name column and
let the Description
column automatically wrap. It's better that the description uses multiple
rows than the symbol names.
I changed the first column from width: 150pt;
Am 22.12.2012 00:46, schrieb Andrei Alexandrescu:
On 12/21/12 7:24 AM, Sönke Ludwig wrote:
Example generated site is here:
http://vibed.org/temp/d-programming-language.org/phobos/index.html
Is any further work on this desired?
Thanks for this work! Let me provide a little feedback. I'm
On 2012-12-21 13:24, Sönke Ludwig wrote:
Is any further work on this desired? If so, what would be the next steps to
integrate it into the
general dlang.org workflow? (or rather, how is that workflow in terms of folder
structure, build
scripts etc.?)
It would also need a phase of bug fixing
On 12/22/12 10:16 AM, Jacob Carlborg wrote:
On 2012-12-21 13:24, Sönke Ludwig wrote:
Is any further work on this desired? If so, what would be the next
steps to integrate it into the
general dlang.org workflow? (or rather, how is that workflow in terms
of folder structure, build
scripts etc.?)
* There's lots of wasted real estate at the top of the page: the source,
license, and authors
sections are way spaced. They should compactly fill the top of the page.
I'll try to get closer to the original there. There are some differences
because the current pages
use a lot of
On 12/22/12 11:49 AM, Sönke Ludwig wrote:
* There's lots of wasted real estate at the top of the page: the source,
license, and authors
sections are way spaced. They should compactly fill the top of the page.
I'll try to get closer to the original there. There are some differences
because
Am 22.12.2012 17:49, schrieb Sönke Ludwig:
Continuing the thought of screen real estate - shouldn't these sections
better be at the _bottom_ of
the page? After all they are just noise for the typical reader and since the
pages are not as long
anymore, they still won't get drowned by the
On 12/22/12 12:53 PM, Sönke Ludwig wrote:
Am 22.12.2012 17:49, schrieb Sönke Ludwig:
Continuing the thought of screen real estate - shouldn't these sections better
be at the _bottom_ of
the page? After all they are just noise for the typical reader and since the
pages are not as long
On Saturday, 22 December 2012 at 17:54:29 UTC, Sönke Ludwig wrote:
In the latest upload a number of items is addressed:
- vertical margins at the top
- redundant column headers
- +/- signs for the package tree
- jumps to line numbers on github (which are off because of
changes after the
Am 22.12.2012 19:13, schrieb Andrei Alexandrescu:
On 12/22/12 12:53 PM, Sönke Ludwig wrote:
Am 22.12.2012 17:49, schrieb Sönke Ludwig:
Continuing the thought of screen real estate - shouldn't these sections
better be at the _bottom_ of
the page? After all they are just noise for the typical
Am 22.12.2012 19:20, schrieb Jacob Carlborg:
On Saturday, 22 December 2012 at 17:54:29 UTC, Sönke Ludwig wrote:
In the latest upload a number of items is addressed:
- vertical margins at the top
- redundant column headers
- +/- signs for the package tree
- jumps to line numbers on
On 12/22/12 12:53 PM, Sönke Ludwig wrote:
Am 22.12.2012 17:49, schrieb Sönke Ludwig:
Continuing the thought of screen real estate - shouldn't these sections better
be at the _bottom_ of
the page? After all they are just noise for the typical reader and since the
pages are not as long
Am 22.12.2012 19:56, schrieb Andrei Alexandrescu:
On 12/22/12 12:53 PM, Sönke Ludwig wrote:
Am 22.12.2012 17:49, schrieb Sönke Ludwig:
Continuing the thought of screen real estate - shouldn't these sections
better be at the _bottom_ of
the page? After all they are just noise for the typical
On Friday, 21 December 2012 at 18:31:48 UTC, Sönke Ludwig wrote:
Am 21.12.2012 18:05, schrieb Andrei Alexandrescu:
(...)
The cheat sheet in std.algorithm is unnecessary (though I
liked the brief examples), but there's a
lot of value in the symbols grouped by category (searching,
comparison,
On Friday, 21 December 2012 at 21:58:34 UTC, Jacob Carlborg wrote:
On 2012-12-21 18:05, Andrei Alexandrescu wrote:
s/remove/integrate/
s/ugly/awesome/
It's ugly that they are manually created. Over 300 lines of
comments that the doc generator should be doing automatically.
I would say that
On 12/22/12 5:10 PM, foobar wrote:
On Friday, 21 December 2012 at 21:58:34 UTC, Jacob Carlborg wrote:
On 2012-12-21 18:05, Andrei Alexandrescu wrote:
s/remove/integrate/
s/ugly/awesome/
It's ugly that they are manually created. Over 300 lines of comments
that the doc generator should be
I don't know if this has been mentioned yet, but some modules
have a link to the source while others do not. I suppose that's a
problem with the documentation itself not including a link. I'm
just mentioning this in case it has something to do with the
formatting.
--rt
Am 23.12.2012 00:11, schrieb Rob T:
I don't know if this has been mentioned yet, but some modules have a link to
the source while others
do not. I suppose that's a problem with the documentation itself not
including a link. I'm just
mentioning this in case it has something to do with the
Am 11.12.2012 22:13, schrieb Andrei Alexandrescu:
On 12/11/12 3:54 PM, Rob T wrote:
On Monday, 10 December 2012 at 22:33:49 UTC, 1100110 wrote:
On 12/10/2012 05:16 AM, Mr. Anonymous wrote:
On Monday, 10 December 2012 at 02:10:43 UTC, Ellery Newcomer wrote:
Is anyone else noticing e.g.
On 12/21/12, Sönke Ludwig slud...@outerproduct.org wrote:
Is any further work on this desired?
The start of the code section needs to be moved a little bit to the
right so the text doesn't appear to touch the edge:
http://i.imgur.com/VuXE1.png
And maybe the color scheme should match the one
On 2012-12-21 13:24, Sönke Ludwig wrote:
Example generated site is here:
http://vibed.org/temp/d-programming-language.org/phobos/index.html
Is any further work on this desired? If so, what would be the next steps to
integrate it into the
general dlang.org workflow? (or rather, how is that
12/21/2012 4:24 PM, Sönke Ludwig пишет:
Am 11.12.2012 22:13, schrieb Andrei Alexandrescu:
Do whom do we talk about Borging the vibe dox into dlang.org?
Andrei
[snip]
Example generated site is here:
http://vibed.org/temp/d-programming-language.org/phobos/index.html
Like it!
--
Am 21.12.2012 15:20, schrieb Andrej Mitrovic:
On 12/21/12, Sönke Ludwig slud...@outerproduct.org wrote:
Is any further work on this desired?
The start of the code section needs to be moved a little bit to the
right so the text doesn't appear to touch the edge:
http://i.imgur.com/VuXE1.png
On 12/21/12 10:43 AM, Jacob Carlborg wrote:
On 2012-12-21 13:24, Sönke Ludwig wrote:
Example generated site is here:
http://vibed.org/temp/d-programming-language.org/phobos/index.html
Is any further work on this desired? If so, what would be the next
steps to integrate it into the
general
On Fri, Dec 21, 2012 at 12:05:47PM -0500, Andrei Alexandrescu wrote:
On 12/21/12 10:43 AM, Jacob Carlborg wrote:
On 2012-12-21 13:24, Sönke Ludwig wrote:
Example generated site is here:
http://vibed.org/temp/d-programming-language.org/phobos/index.html
Is any further work on this
On Friday, 21 December 2012 at 17:23:41 UTC, H. S. Teoh wrote:
+1. The blob of links generated by JS at the top of the current
pages is
(1) ugly, and (2) useless. Grouping symbols by category is by
far more
useful. We need to keep that.
Yes, a category list is far more useful. The best the
On Fri, Dec 21, 2012 at 07:20:16PM +0100, Rob T wrote:
On Friday, 21 December 2012 at 17:23:41 UTC, H. S. Teoh wrote:
+1. The blob of links generated by JS at the top of the current pages
is (1) ugly, and (2) useless. Grouping symbols by category is by far
more useful. We need to keep that.
Am 21.12.2012 18:05, schrieb Andrei Alexandrescu:
(...)
The cheat sheet in std.algorithm is unnecessary (though I liked the brief
examples), but there's a
lot of value in the symbols grouped by category (searching, comparison, ...)
at the top. So we need
to have a means to group things
On 2012-12-21 18:05, Andrei Alexandrescu wrote:
s/remove/integrate/
s/ugly/awesome/
It's ugly that they are manually created. Over 300 lines of comments
that the doc generator should be doing automatically. I would say that
is far from awesome.
--
/Jacob Carlborg
On 2012-12-21 19:31, Sönke Ludwig wrote:
What also would be nice is to have the methods inline, expandable.
Would that mean the Classes/Structs/... tables as f.ex. in std.datetime?
So there would be a small clickable thing and all members would fly out below
it as direct links?
and possibly
On 12/21/12 7:24 AM, Sönke Ludwig wrote:
Example generated site is here:
http://vibed.org/temp/d-programming-language.org/phobos/index.html
Is any further work on this desired?
Thanks for this work! Let me provide a little feedback. I'm looking
mainly at std.array and std.algorithm.
*
On 12/21/12 6:46 PM, Andrei Alexandrescu wrote:
[snip]
Forgot to emphasize what I already mentioned: alphabetic order is okay,
but I wonder how we can integrate that with grouping per functionality
area (the way std.algorithm does).
Andrei
Andrei Alexandrescu:
Thanks for this work! Let me provide a little feedback. I'm
looking mainly at std.array and std.algorithm.
Compare a page like this:
http://dlang.org/phobos/std_array.html
With the docs of the Prelude module of Haskell:
On Fri, 21 Dec 2012, Andrei Alexandrescu wrote:
* But by very, very far the community-contributed stuff is just perfect. I
really really really hope we can get something like that integrated. There are
many ways to approach this:
- By integrating a wiki page via e.g. an IFRAME.
- By
On Friday, 21 December 2012 at 23:46:05 UTC, Andrei Alexandrescu
wrote:
* Module in the title is redundant I guess.
I don't think it is redundant because when you are looking at a
page, the module as the title instantly tells you (or reminds
you) what module you are looking at, otherwise
On Saturday, 22 December 2012 at 00:00:43 UTC, Brad Roberts wrote:
The current separate wiki pages that mirror the dlang site are
the worse
of both worlds in that the content exists, is hardly ever
folded in, and
isn't even visible along side the page but hidden off behind a
link that I
bet
On 12/21/12 7:16 PM, Brad Roberts wrote:
I love community / croudsourcing. But where it falls down in most of the
examples I've seen is that the majority of the feedback / comments really
belong as edits to the actual content, not additional notes. We need to
aim for making both happen, imho.
On 12/21/12 7:29 PM, Rob T wrote:
On Friday, 21 December 2012 at 23:46:05 UTC, Andrei Alexandrescu wrote:
* Module in the title is redundant I guess.
I don't think it is redundant because when you are looking at a page,
the module as the title instantly tells you (or reminds you) what
On 12/21/12 7:52 PM, Rob T wrote:
On Saturday, 22 December 2012 at 00:00:43 UTC, Brad Roberts wrote:
The current separate wiki pages that mirror the dlang site are the worse
of both worlds in that the content exists, is hardly ever folded in, and
isn't even visible along side the page but
On 12/10/2012 2:31 PM, 1100110 wrote:
I've had dail-up, I've had satelite internet.
Only is indeed the appropriate word to use.
I've had floppy disks :-)
It's still hard to get used to the superfast disks we have these days.
On Saturday, 22 December 2012 at 02:36:44 UTC, Andrei
Alexandrescu wrote:
I was referring only to the actual word.
Ah I see, but it's still debatable to remove, although not a big
deal either way.
Behold: http://us3.php.net/manual/en/function.exp.php
I understand what you mean now,
On 12/21/12 10:27 PM, Rob T wrote:
Behold: http://us3.php.net/manual/en/function.exp.php
I understand what you mean now, just didn't at first. What I see looks
very good in the php page.
I think there's a lot to be said about the contribution of PHP's
excellent documentation to the success
On Saturday, 22 December 2012 at 03:34:55 UTC, Andrei
Alexandrescu wrote:
On 12/21/12 10:27 PM, Rob T wrote:
Behold: http://us3.php.net/manual/en/function.exp.php
I understand what you mean now, just didn't at first. What I
see looks
very good in the php page.
I think there's a lot to be
Am 11.12.2012 22:13, schrieb Andrei Alexandrescu:
On 12/11/12 3:54 PM, Rob T wrote:
On Monday, 10 December 2012 at 22:33:49 UTC, 1100110 wrote:
On 12/10/2012 05:16 AM, Mr. Anonymous wrote:
On Monday, 10 December 2012 at 02:10:43 UTC, Ellery Newcomer wrote:
Is anyone else noticing e.g.
On Tuesday, 11 December 2012 at 21:41:10 UTC, Pragma Tix wrote:
Soenke Ludwig, or ask here
http://news.rejectedsoftware.com/groups/rejectedsoftware.vibed/
IMO dlang should be powered by vibe.d
If Vibe.d is stable enough at this point (it's a WIP) then yes
that would be a good idea, and a
On Mon, Dec 10, 2012 at 04:54:43PM -0500, Nick Sabalausky wrote:
On Mon, 10 Dec 2012 12:57:43 -0800
H. S. Teoh hst...@quickfur.ath.cx wrote:
[...]
Heh. I used to browse with no JS. But due to the annoying bandwagon
jumping trend that is a common pathology in people involved with
computers,
On Monday, 10 December 2012 at 22:33:49 UTC, 1100110 wrote:
On 12/10/2012 05:16 AM, Mr. Anonymous wrote:
On Monday, 10 December 2012 at 02:10:43 UTC, Ellery Newcomer
wrote:
Is anyone else noticing e.g. std.datetime taking upwards of
30 seconds
to render the blob of links at the top? It's
On 12/11/12 3:54 PM, Rob T wrote:
On Monday, 10 December 2012 at 22:33:49 UTC, 1100110 wrote:
On 12/10/2012 05:16 AM, Mr. Anonymous wrote:
On Monday, 10 December 2012 at 02:10:43 UTC, Ellery Newcomer wrote:
Is anyone else noticing e.g. std.datetime taking upwards of 30 seconds
to render the
On Tuesday, 11 December 2012 at 21:13:25 UTC, Andrei Alexandrescu
wrote:
On 12/11/12 3:54 PM, Rob T wrote:
On Monday, 10 December 2012 at 22:33:49 UTC, 1100110 wrote:
On 12/10/2012 05:16 AM, Mr. Anonymous wrote:
On Monday, 10 December 2012 at 02:10:43 UTC, Ellery Newcomer
wrote:
Is anyone
10.12.2012 6:10, Ellery Newcomer пишет:
Is anyone else noticing e.g. std.datetime taking upwards of 30 seconds
to render the blob of links at the top? It's freakin freezing my entire
browser.
Personally I disable JavaScript for dlang.org a long time ago and happy
now. At least because the
On Monday, 10 December 2012 at 03:18:30 UTC, 1100110 wrote:
On 12/09/2012 08:10 PM, Ellery Newcomer wrote:
The whole process only takes 5-7 seconds here.
Only is not the right word to use here.
On Monday, 10 December 2012 at 02:10:43 UTC, Ellery Newcomer
wrote:
Is anyone else noticing e.g. std.datetime taking upwards of 30
seconds to render the blob of links at the top? It's freakin
freezing my entire browser.
ddox* on dlang.org, anyone?
http://vibed.org/temp/phobos/index.html
*
On Sun, 09 Dec 2012 18:10:42 -0800
Ellery Newcomer ellery-newco...@utulsa.edu wrote:
Is anyone else noticing e.g. std.datetime taking upwards of 30
seconds to render the blob of links at the top? It's freakin freezing
my entire browser.
It only takes about a second or two for me in FF2. I'm
On Mon, Dec 10, 2012 at 12:34:13PM -0500, Nick Sabalausky wrote:
On Sun, 09 Dec 2012 18:10:42 -0800
Ellery Newcomer ellery-newco...@utulsa.edu wrote:
Is anyone else noticing e.g. std.datetime taking upwards of 30
seconds to render the blob of links at the top? It's freakin freezing
my
On Mon, 10 Dec 2012 09:45:06 -0800
H. S. Teoh hst...@quickfur.ath.cx wrote:
On Mon, Dec 10, 2012 at 12:34:13PM -0500, Nick Sabalausky wrote:
On Sun, 09 Dec 2012 18:10:42 -0800
Ellery Newcomer ellery-newco...@utulsa.edu wrote:
Is anyone else noticing e.g. std.datetime taking upwards of
On Mon, Dec 10, 2012 at 01:58:30PM -0500, Nick Sabalausky wrote:
On Mon, 10 Dec 2012 09:45:06 -0800
H. S. Teoh hst...@quickfur.ath.cx wrote:
On Mon, Dec 10, 2012 at 12:34:13PM -0500, Nick Sabalausky wrote:
On Sun, 09 Dec 2012 18:10:42 -0800
Ellery Newcomer ellery-newco...@utulsa.edu
On Mon, 10 Dec 2012 12:57:43 -0800
H. S. Teoh hst...@quickfur.ath.cx wrote:
On Mon, Dec 10, 2012 at 01:58:30PM -0500, Nick Sabalausky wrote:
On Mon, 10 Dec 2012 09:45:06 -0800
H. S. Teoh hst...@quickfur.ath.cx wrote:
'cos you're running with JS turned off. :-)
g
It makes
On Mon, 10 Dec 2012 11:54:52 +0100
Peter Alexander peter.alexander...@gmail.com wrote:
On Monday, 10 December 2012 at 03:18:30 UTC, 1100110 wrote:
On 12/09/2012 08:10 PM, Ellery Newcomer wrote:
The whole process only takes 5-7 seconds here.
Only is not the right word to use here.
Yea,
On 12/10/2012 05:16 AM, Mr. Anonymous wrote:
On Monday, 10 December 2012 at 02:10:43 UTC, Ellery Newcomer wrote:
Is anyone else noticing e.g. std.datetime taking upwards of 30 seconds
to render the blob of links at the top? It's freakin freezing my
entire browser.
ddox* on dlang.org, anyone?
On 12/10/2012 04:20 PM, Nick Sabalausky wrote:
On Mon, 10 Dec 2012 11:54:52 +0100
Peter Alexanderpeter.alexander...@gmail.com wrote:
On Monday, 10 December 2012 at 03:18:30 UTC, 1100110 wrote:
On 12/09/2012 08:10 PM, Ellery Newcomer wrote:
The whole process only takes 5-7 seconds here.
Is anyone else noticing e.g. std.datetime taking upwards of 30 seconds
to render the blob of links at the top? It's freakin freezing my entire
browser.
On Sunday, December 09, 2012 18:10:42 Ellery Newcomer wrote:
Is anyone else noticing e.g. std.datetime taking upwards of 30 seconds
to render the blob of links at the top? It's freakin freezing my entire
browser.
The link situation definitely needs to be fixed. People keep making noise
abouet
On 12/09/2012 08:10 PM, Ellery Newcomer wrote:
Is anyone else noticing e.g. std.datetime taking upwards of 30 seconds
to render the blob of links at the top? It's freakin freezing my entire
browser.
Yeah, I see it.
Not browser stalling though, just annoying.
It renders without the links,
Can we get this updated? std.traits.ParameterIdentifierTuple and
std.traits.ParameterDefaultValueTuple are not showing up, but have been
around at least since 2.060 was released
On Wednesday, November 14, 2012 06:40:54 Ellery Newcomer wrote:
Can we get this updated? std.traits.ParameterIdentifierTuple and
std.traits.ParameterDefaultValueTuple are not showing up, but have been
around at least since 2.060 was released
They don't have ddoc comments, just normal comments.
On 11/14/12, Ellery Newcomer ellery-newco...@utulsa.edu wrote:
Can we get this updated? std.traits.ParameterIdentifierTuple and
std.traits.ParameterDefaultValueTuple are not showing up, but have been
around at least since 2.060 was released
Related
85 matches
Mail list logo
