On Thu, 2013-08-15 at 20:20 +0100, Bruno Medeiros wrote:
A new version of DDT - D Development tools is out.
The major change is the new parser which is updated to the latest
version of D, and is much more robust than the previous one.
Full changelog/info here:
On 2013-08-15 21:20, Bruno Medeiros wrote:
A new version of DDT - D Development tools is out.
The major change is the new parser which is updated to the latest
version of D, and is much more robust than the previous one.
Full changelog/info here:
On 16/08/2013 11:12, Russel Winder wrote:
On Thu, 2013-08-15 at 20:20 +0100, Bruno Medeiros wrote:
A new version of DDT - D Development tools is out.
The major change is the new parser which is updated to the latest
version of D, and is much more robust than the previous one.
Full
On Fri, 2013-08-16 at 13:08 +0200, Jacob Carlborg wrote:
[…]
I downloaded the standard version of Kepler. Then I followed the
installation instructions. But after the restart I don't see anything
related to DDT/D in the preferences.
I installed into Juno which seems to work fine, I have no
On 16/08/2013 12:08, Jacob Carlborg wrote:
On 2013-08-15 21:20, Bruno Medeiros wrote:
A new version of DDT - D Development tools is out.
The major change is the new parser which is updated to the latest
version of D, and is much more robust than the previous one.
Full changelog/info here:
On 16/08/2013 13:03, Russel Winder wrote:
The single biggest problem with Eclipse is the annual upgrade marathon.
Since nothing carries over from one installation to another you have to
go through the whole rigmarole to install all the extras, every year. I
wonder whether to stay with Juno and
On 15/08/2013 20:20, Bruno Medeiros wrote:
A new version of DDT - D Development tools is out.
The major change is the new parser which is updated to the latest
version of D, and is much more robust than the previous one.
Full changelog/info here:
On Fri, 2013-08-16 at 14:19 +0100, Bruno Medeiros wrote:
[…]
If you add the update site for the new Eclipse release (for example
http://download.eclipse.org/releases/kepler for Kepler) to your current
installation, and run the Check for Updates it should update Eclipse
and retain all the
On 15/08/2013 20:25, Andrei Alexandrescu wrote:
On 8/15/13 12:20 PM, Bruno Medeiros wrote:
A new version of DDT - D Development tools is out.
The major change is the new parser which is updated to the latest
version of D, and is much more robust than the previous one.
Full changelog/info here:
On 8/16/13 12:14 PM, Bruno Medeiros wrote:
I've updated the Features wiki with new screenshots, and revised the
text to be more clear:
http://code.google.com/p/ddt/wiki/Features
(like removing the A JDT-like project model references which actually
doesn't mean anything to people who are not
W dniu 16.08.2013 15:32, Bruno Medeiros pisze:
On 15/08/2013 22:07, Piotr Szturmaj wrote:
W dniu 15.08.2013 21:20, Bruno Medeiros pisze:
A new version of DDT - D Development tools is out.
The major change is the new parser which is updated to the latest
version of D, and is much more robust
On Thursday, 15 August 2013 at 02:30:42 UTC, Jonathan M Davis
wrote:
On Wednesday, August 14, 2013 22:56:30 Andre Artus wrote:
As with many things it depends on what you want to achieve.
Answering on SO is as much about establishing awareness as it
is
about answering the question. For a
On Friday, 16 August 2013 at 05:48:12 UTC, Kagamin wrote:
On Friday, 9 August 2013 at 17:00:53 UTC, deadalnix wrote:
It is ambiguous if the inout of the function passed as
parameter stand for the function passed as parameter or the
function you pass the parameter to.
See my explanation, how
Andrei Alexandrescu wrote:
On 8/15/13 12:42 PM, Adam D. Ruppe wrote:
On Thursday, 15 August 2013 at 18:35:22 UTC, Joakim wrote:
I've only done X11 forwarding over ssh, both WAN and LAN, it was
incredibly laggy in both cases.
You're probably using bloated apps! I'm using my crappygui.d on
A very interesting talk done as if we were in the mid-70's
discussing the future of programming in 40 years time (meaning
today).
http://vimeo.com/71278954
The main message is how fast technology changes and how
developers resist to change specially in the presence of dogmas.
--
Paulo
On Wednesday, 14 August 2013 at 17:35:28 UTC, BLM768 wrote:
The current behavior of placing identically-named functions
from separate mixins into separate overload sets works well
most of the time, but there are cases when the functions should
be in the same overload set, and the aliasing
On Friday, 16 August 2013 at 07:48:52 UTC, QAston wrote:
On Wednesday, 14 August 2013 at 17:35:28 UTC, BLM768 wrote:
The current behavior of placing identically-named functions
from separate mixins into separate overload sets works well
most of the time, but there are cases when the functions
Brad Anderson e...@gnuk.net wrote in message
news:vdiwuykbulxauiabw...@forum.dlang.org...
On Thursday, 15 August 2013 at 14:11:02 UTC, Daniel Murphy wrote:
Suliman bubnenk...@gmail.com wrote in message
news:htihsekthjkyhqazu...@forum.dlang.org...
Does anybody work on port D to D?
I've done
H. S. Teoh hst...@quickfur.ath.cx wrote in message
news:mailman.91.1376592874.1719.digitalmar...@puremagic.com...
On Thu, Aug 15, 2013 at 08:19:06PM +0200, Brad Anderson wrote:
On Thursday, 15 August 2013 at 14:11:02 UTC, Daniel Murphy wrote:
[...]
I am currently able to convert the C++
Andrei Alexandrescu seewebsiteforem...@erdani.org wrote in message
news:kuj10l$194l$1...@digitalmars.com...
On 8/15/13 7:10 AM, Daniel Murphy wrote:
Suliman bubnenk...@gmail.com wrote in message
news:htihsekthjkyhqazu...@forum.dlang.org...
Does anybody work on port D to D?
I've done quite a
On Friday, August 16, 2013 18:54:41 Daniel Murphy wrote:
Yep, all the fun parts are done and the rest should be fairly tedious.
LOL. I guess that that's kind of where I am with splitting std.datetime. It's
basically done code-wise, but now I have to fix all of the documentation, which
is no
Kagamin s...@here.lot wrote in message
news:iceiqyqtdsippewge...@forum.dlang.org...
Isn't the resulting D code is still one 70k-line file?
~92k
Putting the code into multiple files is trivial, but until we've done some
major refactoring it won't start to resemble the original source
On Friday, 16 August 2013 at 09:28:13 UTC, Daniel Murphy wrote:
Kagamin s...@here.lot wrote in message
news:iceiqyqtdsippewge...@forum.dlang.org...
Isn't the resulting D code is still one 70k-line file?
~92k
Putting the code into multiple files is trivial, but until
we've done some
major
On Fri, 2013-08-16 at 04:21 +0200, Atash wrote:
[…]
Clarifying question:
At what level is this interest pointed at? Is it at the level of
assembly/IL and other scary stuff, or is it at creating bindings
that are cleaner and providing more convenient tools?
Assembly language and other
On Aug 16, 2013 10:55 AM, BS slackov...@gmail.com wrote:
On Friday, 16 August 2013 at 09:28:13 UTC, Daniel Murphy wrote:
Kagamin s...@here.lot wrote in message
news:iceiqyqtdsippewge...@forum.dlang.org...
Isn't the resulting D code is still one 70k-line file?
~92k
Putting the code into
On Friday, 16 August 2013 at 10:04:22 UTC, Russel Winder wrote:
[...]
The core (!) point here is that processor chips are rapidly
becoming a
collection of heterogeneous cores. Any programming language
that assumes
a single CPU or a collection of homogeneous CPUs has built-in
obsolescence.
So
Iain Buclaw ibuc...@ubuntu.com wrote in message
news:mailman.100.1376649733.1719.digitalmar...@puremagic.com...
On Aug 16, 2013 10:55 AM, BS slackov...@gmail.com wrote:
On Friday, 16 August 2013 at 09:28:13 UTC, Daniel Murphy wrote:
Kagamin s...@here.lot wrote in message
On 08/16/2013 12:42 PM, Iain Buclaw wrote:
I suspect we won't be able to do that efficiently until Don starts
speeding up CTFE. ;-)
Using, of course, only CTFE-able language constructs.
On 16 August 2013 04:39, bearophile bearophileh...@lycos.com wrote:
The XMM registers I am using are efficient when you feed them memory from
arrays aligned to 16 bytes, as the D GC produces. But the YMM registers
used by the AVX/AVX2 instructions prefer an alignment of 32 bytes. And the
On Fri, 2013-08-16 at 12:41 +0200, Paul Jurczak wrote:
[…]
It seems to me that you are describing something similar to C++
AMP, which is a high level, language specific solution to GPGPU
problem.
C++ AMP may be an open specification but it only targets DirectX. But
the ideas behind it are very
On 08/13/2013 12:48 AM, H. S. Teoh wrote:
But you're missing the bigger picture. What I envision is that this D
build tool will go beyond merely building DMD/druntime/Phobos. If it's
successful, it can become the *standard* D build tool for all D
programs. Having a standard D build tool will
On Thursday, 15 August 2013 at 18:35:22 UTC, Joakim wrote:
I've only done X11 forwarding over ssh, both WAN and LAN, it
was incredibly laggy in both cases.
As Andrei and I have pointed out, NX does a much better job of
things. If nothing else, read the explanation of how it works--
there
On 08/16/2013 12:04 PM, Russel Winder wrote:
I guess my question is whether people are interested in std.gpgpu (or
some more sane name).
Yes, I'd be interested, particularly if it's possible to produce a GPGPU
solution that is much more user-friendly than the current C/C++ options.
I think
On Thursday, 15 August 2013 at 18:52:21 UTC, H. S. Teoh wrote:
You need to run ssh -C, otherwise it just goes uncompressed
plus the
overhead of encrypting/decrypting each packet.
SSH compression is something of a worst-case scenario for
compressing remote X traffic. As a fun aside, for X
On Friday, 16 August 2013 at 07:19:09 UTC, Marek Janukowicz wrote:
If we are discussing X's shortcomings: why don't we use
something like http://wayland.freedesktop.org/
I don't have it installed on my computer! I do have X though.
BTW, my minigui.d (previously crappygui.d) is moving along at
On Thursday, 15 August 2013 at 20:09:34 UTC, Jonas Drewsen wrote:
* SDL for input - would be awesome to get rid of this by using
some of AdamRuppes work maybe.
heh, I'm *almost* to the point where I can replace SDL for my
own little games. I ported stb_truetype.h to D earlier in the
week, I
On Friday, 16 August 2013 at 07:48:52 UTC, QAston wrote:
You can put those functions into HasOtherMixins by using alias.
struct HasOtherMixins {
...
alias someMixin!int.abc abc;
alias someMixin!float.abc abc;
alias someOtherMixin abc;
}
Actually, that syntax only works for regular templates,
Denis has been complaining about this for ages and I think it's
worth doing something about.
Definitions:
std.typecons.Tuple
A bit like python's tuples. It's a heterogeneous collection of
runtime values with compile-time determined types.
std.typetuple.TypeTuple
A heterogeneous
I would like to contribute to the D ecosystem, but as I'm still
in the learning process I do not want to get my sticky fingers
all over someones nice clean code.
I have poured over the documentation and see that there are a few
low-hanging fruit that I would like to pluck. So I have decided
John Colvin:
Possible solutions:
My vote is for solution n.5:
Add the built-in t{} syntax to denote all kind of tuples.
Bye,
bearophile
On Friday, 16 August 2013 at 16:08:42 UTC, bearophile wrote:
John Colvin:
Possible solutions:
My vote is for solution n.5:
Add the built-in t{} syntax to denote all kind of tuples.
This. With an exception of I don't care what syntax is.
There has been a thread in D.learn by Ali recently
On Friday, 16 August 2013 at 16:08:42 UTC, bearophile wrote:
John Colvin:
Possible solutions:
My vote is for solution n.5:
Add the built-in t{} syntax to denote all kind of tuples.
Bye,
bearophile
There was no number 5...
A builtin syntax would be cool, I agree.
On Friday, 16 August 2013 at 16:07:59 UTC, Andre Artus wrote:
I would like to contribute to the D ecosystem, but as I'm still
in the learning process I do not want to get my sticky fingers
all over someones nice clean code.
I have poured over the documentation and see that there are a
few
On Fri, Aug 16, 2013 at 06:08:36PM +0200, bearophile wrote:
John Colvin:
Possible solutions:
My vote is for solution n.5:
Add the built-in t{} syntax to denote all kind of tuples.
[...]
This can be part of the solution, but by itself is not good enough,
because the so-called typetuple
On Friday, 16 August 2013 at 16:07:59 UTC, Andre Artus wrote:
I would like to contribute to the D ecosystem, but as I'm still
in the learning process I do not want to get my sticky fingers
all over someones nice clean code.
I have poured over the documentation and see that there are a
few
On Friday, 16 August 2013 at 16:07:59 UTC, Andre Artus wrote:
I would like to contribute to the D ecosystem, but as I'm still
in the learning process I do not want to get my sticky fingers
all over someones nice clean code.
I have poured over the documentation and see that there are a
few
On 8/16/13 9:22 AM, Dicebot wrote:
On Friday, 16 August 2013 at 16:07:59 UTC, Andre Artus wrote:
I would like to contribute to the D ecosystem, but as I'm still in the
learning process I do not want to get my sticky fingers all over
someones nice clean code.
I have poured over the
Manu:
I'm not sure about the warning, it doesn't really sound right
to me. Maybe
it would be useful... or maybe it would be annoying.
A cast is a cast, it is a deliberate act of reinterpretation...
the user
needs to take some responsibility in this case.
OK.
What happens if you do:
On Fri, Aug 16, 2013 at 06:29:40PM +0200, Craig Dillabaugh wrote:
On Friday, 16 August 2013 at 16:07:59 UTC, Andre Artus wrote:
I would like to contribute to the D ecosystem, but as I'm still in
the learning process I do not want to get my sticky fingers all
over someones nice clean code.
I
On Friday, 16 August 2013 at 16:36:16 UTC, Andrei Alexandrescu
wrote:
Just use this forum and plant e.g. [dox] in the title.
Andrei
Why prefer less structured and inconvenient approach to an
organized one? :) digitalmars.D is not that quite these days and
discussing formal spec definitions
On Friday, 16 August 2013 at 16:53:47 UTC, H. S. Teoh wrote:
+1.
/snip
s/\+1/\+2/ to everything. Might encourage me to get back to my
own doc stuff.
-Wyatt
On 8/16/13 10:12 AM, Dicebot wrote:
On Friday, 16 August 2013 at 16:36:16 UTC, Andrei Alexandrescu wrote:
Just use this forum and plant e.g. [dox] in the title.
Andrei
Why prefer less structured and inconvenient approach to an organized
one? :) digitalmars.D is not that quite these days and
On Friday, 16 August 2013 at 16:07:59 UTC, Andre Artus wrote:
I would like to contribute to the D ecosystem, but as I'm still
in the learning process I do not want to get my sticky fingers
all over someones nice clean code.
I have poured over the documentation and see that there are a
few
On Friday, 16 August 2013 at 17:41:19 UTC, Andrei Alexandrescu
wrote:
The converse risk is balkanization. We already have subgroups
that are effectively dead, for which similar arguments were
made in the past.
Problem with current subgroups is that they are created on topic
basis, not to
On 8/16/13 10:56 AM, Dicebot wrote:
On Friday, 16 August 2013 at 17:41:19 UTC, Andrei Alexandrescu wrote:
The converse risk is balkanization. We already have subgroups that are
effectively dead, for which similar arguments were made in the past.
Problem with current subgroups is that they are
On Friday, 16 August 2013 at 16:28:29 UTC, H. S. Teoh wrote:
I think a good start is to call them by different names. The
word
tuple is just too overloaded right now, and using the same
term to
refer to two incompatible things is just formula for endless
confusion.
Sequence is OK, but risks
On 08/16/2013 09:27 AM, H. S. Teoh wrote:
The so-called typetuple (what dmd calls a tuple) is a compile-time
construct that can contain types, aliases, compile-time values, etc.,
that only exist at compile-time.
They are all symbols, right? And symbols live only at compile time.
...
H. S. Teoh wrote:
Most Phobos modules suffer from this problem. The first
paragraph often just says something to the effect of this is
module X (we already know that) and it contains Y, Z, W (we can
see that already). Very unhelpful. We need descriptions of:
1) What: what this module does --
On Fri, Aug 16, 2013 at 11:10:28AM -0700, Ali Çehreli wrote:
On 08/16/2013 09:27 AM, H. S. Teoh wrote:
The so-called typetuple (what dmd calls a tuple) is a
compile-time construct that can contain types, aliases, compile-time
values, etc., that only exist at compile-time.
They are all
On Friday, 16 August 2013 at 18:09:04 UTC, Andrei Alexandrescu
wrote:
On 8/16/13 10:56 AM, Dicebot wrote:
On Friday, 16 August 2013 at 17:41:19 UTC, Andrei Alexandrescu
wrote:
The converse risk is balkanization. We already have subgroups
that are
effectively dead, for which similar arguments
On 08/16/2013 11:21 AM, H. S. Teoh wrote:
On Fri, Aug 16, 2013 at 11:10:28AM -0700, Ali Çehreli wrote:
On 08/16/2013 09:27 AM, H. S. Teoh wrote:
The so-called typetuple (what dmd calls a tuple) is a
compile-time construct that can contain types, aliases, compile-time
values, etc., that
On Friday, 16 August 2013 at 16:28:29 UTC, H. S. Teoh wrote:
This can be part of the solution, but by itself is not good
enough,
because the so-called typetuple and std.typecons.
Key point is that having proper built-in syntax for
type/expression tuples obsoletes the need in TypeTuple and it
On Friday, 16 August 2013 at 18:10:29 UTC, Ali Çehreli wrote:
On 08/16/2013 09:27 AM, H. S. Teoh wrote:
The so-called typetuple (what dmd calls a tuple) is a
compile-time
construct that can contain types, aliases, compile-time
values, etc.,
that only exist at compile-time.
They are all
On Friday, 16 August 2013 at 18:09:04 UTC, Andrei Alexandrescu
wrote:
The argument is built from a mistaken angle. Thinking of doing
some work on docs in the future, let's create a group for docs!
Things should happen organically, i.e. creating a specialized
group should follow a need
On Friday, 16 August 2013 at 16:19:51 UTC, Dicebot wrote:
Add the built-in t{} syntax to denote all kind of tuples.
This. With an exception of I don't care what syntax is.
/snip
What was the general attitude to http://wiki.dlang.org/DIP32 ?
I don't like the t. I'd prefer just using
On 8/16/13 10:56 AM, Dicebot wrote:
it. I'd probably favor deleting such obsolete groups (dtl,
dwt, debugger?) but it is a different topic.
Archive, don't delete.
On Friday, 16 August 2013 at 18:25:02 UTC, Andre Artus wrote:
I understand were you are coming from. And, while I currently
feel
The documentation on the lexical rules for BinaryInteger
(http://dlang.org/lex.html#BinaryInteger) has a few issues:
BinaryInteger:
BinPrefix BinaryDigits
The nonterminal BinaryDigits, does not exist.
BinaryDigitsUS:
BinaryDigitUS
BinaryDigitUS BinaryDigitsUS
The construction
In the documentation
(http://dlang.org/lex.html#HexadecimalInteger) as it currently
stands the HexLetter is specified as including the underscore,
which in a strict interpretation means that the following escape
sequences are allowed:
\x__ (from \x HexDigit HexDigit)
\u (from \u HexDigit
On Friday, 16 August 2013 at 18:12:57 UTC, Andre Artus wrote:
Is there a way to break the pages into a more of a hierarchy,
so that documentation for each module doesn't have to be on one
page? Perhaps a DDOC Section could indicate the category?
Are you familiar with DDOX?
On Friday, August 16, 2013 18:08:36 bearophile wrote:
John Colvin:
Possible solutions:
My vote is for solution n.5:
Add the built-in t{} syntax to denote all kind of tuples.
Since the built-in tuples / std.typetuple.TypeTuple and std.typecons.Tuple
are fundamentally different, I don't see
OK, I got dotComplete working in Vim, but I can't get the
parenComplete calltips. Which cursor position should I give? The
left-paren? The last character of the function name? Right after
the left-paren? I can't seem to get any to work...
On Friday, 16 August 2013 at 19:19:19 UTC, Jonathan M Davis wrote:
Since the built-in tuples / std.typetuple.TypeTuple and
std.typecons.Tuple
are fundamentally different, I don't see how you could possibly
combine the two
in a single syntax. You'd need different syntaxes for each one.
The
On Friday, 16 August 2013 at 19:12:46 UTC, Mr. Anonymous wrote:
On Friday, 16 August 2013 at 18:12:57 UTC, Andre Artus wrote:
Is there a way to break the pages into a more of a hierarchy,
so that documentation for each module doesn't have to be on
one page? Perhaps a DDOC Section could
On Friday, August 16, 2013 10:41:19 Andrei Alexandrescu wrote:
The converse risk is balkanization. We already have subgroups that are
effectively dead, for which similar arguments were made in the past.
Plus, if one of the main complaints with regards to the documentation is that
only a few
On Friday, 16 August 2013 at 18:41:57 UTC, Wyatt wrote:
On 8/16/13 10:56 AM, Dicebot wrote:
it. I'd probably favor deleting such obsolete groups (dtl,
dwt, debugger?) but it is a different topic.
Archive, don't delete.
On Friday, 16 August 2013 at 18:25:02 UTC, Andre Artus wrote:
I
On Friday, 16 August 2013 at 19:27:58 UTC, Andre Artus wrote:
On Friday, 16 August 2013 at 19:12:46 UTC, Mr. Anonymous wrote:
On Friday, 16 August 2013 at 18:12:57 UTC, Andre Artus wrote:
Is there a way to break the pages into a more of a hierarchy,
so that documentation for each module
On Friday, August 16, 2013 21:23:26 Dicebot wrote:
On Friday, 16 August 2013 at 19:19:19 UTC, Jonathan M Davis wrote:
Since the built-in tuples / std.typetuple.TypeTuple and
std.typecons.Tuple
are fundamentally different, I don't see how you could possibly
combine the two
in a single
On Friday, 16 August 2013 at 19:21:53 UTC, Idan Arye wrote:
OK, I got dotComplete working in Vim, but I can't get the
parenComplete calltips. Which cursor position should I give?
The left-paren? The last character of the function name? Right
after the left-paren? I can't seem to get any to
On Friday, 16 August 2013 at 12:18:49 UTC, Russel Winder wrote:
On Fri, 2013-08-16 at 12:41 +0200, Paul Jurczak wrote:
[…]
Today you have to download the kernel to the attached GPGPU
over the
bus. In the near future the GPGPU will exist in a single memory
address
space shared with all the
On Friday, 16 August 2013 at 19:29:46 UTC, Jonathan M Davis wrote:
On Friday, August 16, 2013 10:41:19 Andrei Alexandrescu wrote:
The converse risk is balkanization. We already have subgroups
that are
effectively dead, for which similar arguments were made in the
past.
Plus, if one of the
The core (!) point here is that processor chips are rapidly
becoming a
collection of heterogeneous cores. Any programming language
that assumes
a single CPU or a collection of homogeneous CPUs has built-in
obsolescence.
So the question I am interested in is whether D is the language
that can
On Fri, Aug 16, 2013 at 08:25:00PM +0200, Andre Artus wrote:
On Friday, 16 August 2013 at 18:09:04 UTC, Andrei Alexandrescu
wrote:
[...]
Things should happen organically, i.e. creating a specialized
group should follow a need substantiated by increased volume of
specialized discussion in the
I've been doing some work with the language grammar
specification. You may find these resources useful:
http://d.puremagic.com/issues/show_bug.cgi?id=10233
https://github.com/Hackerpilot/DGrammar/blob/master/D.g4
On Friday, 16 August 2013 at 19:55:56 UTC, luminousone wrote:
The core (!) point here is that processor chips are rapidly
becoming a
collection of heterogeneous cores. Any programming language
that assumes
a single CPU or a collection of homogeneous CPUs has built-in
obsolescence.
So the
On Friday, August 16, 2013 21:57:01 Andre Artus wrote:
It is disheartening to think that the people with potential for
the most valuable contributions or insight will be avoiding
discussions regarding the documentation. But I fear you are
correct.
There's a difference between avoiding
On Fri, Aug 16, 2013 at 03:35:40PM -0400, Jonathan M Davis wrote:
[...]
Adding a syntax for TypeTuple, making TypeTuple redundant would be
great, but Bearophile seems to be arguing that having some sort of
tuple syntax would make it so that we don't need TypeTuple and Tuple,
which is wrong,
On Friday, 16 August 2013 at 17:45:35 UTC, Suliman wrote:
On Friday, 16 August 2013 at 16:07:59 UTC, Andre Artus wrote:
I would like to contribute to the D ecosystem, but as I'm
still in the learning process I do not want to get my sticky
fingers all over someones nice clean code.
I have
On Friday, 16 August 2013 at 19:35:56 UTC, Jonathan M Davis wrote:
But TypeTuple and the built-in ones _aren't_ different.
TypeTuple is an alias
for the built-in ones that's required because of the lack of
syntax for
declaring them on their own.
That is intention but not implementation.
On Friday, 16 August 2013 at 20:22:49 UTC, H. S. Teoh wrote:
...
Term tuple comes from math and means ordered set of elements.
In that sense anonymous struct with unnamed fields _is_ a tuple
and I thing std.typecons.Tuple is the place where naming is fine.
It is re-using the term for
On Friday, 16 August 2013 at 20:12:20 UTC, Jonathan M Davis wrote:
On Friday, August 16, 2013 21:57:01 Andre Artus wrote:
It is disheartening to think that the people with potential for
the most valuable contributions or insight will be avoiding
discussions regarding the documentation. But I
I was just thinking about the whole Tuple situation today. I
think I might write up a quick, somewhat-related post.
As for TypeTuple, I agree that it is not a good name at all for
what it does. It confused me endlessly when I first started
learning D. There are still corner cases where it's
On Fri, Aug 16, 2013 at 04:12:11PM -0400, Jonathan M Davis wrote:
On Friday, August 16, 2013 21:57:01 Andre Artus wrote:
It is disheartening to think that the people with potential for
the most valuable contributions or insight will be avoiding
discussions regarding the documentation. But I
On Friday, August 16, 2013 22:30:11 Dicebot wrote:
On Friday, 16 August 2013 at 20:22:49 UTC, H. S. Teoh wrote:
...
Term tuple comes from math and means ordered set of elements.
In that sense anonymous struct with unnamed fields _is_ a tuple
and I thing std.typecons.Tuple is the place
On Fri, Aug 16, 2013 at 10:24:55PM +0200, Andre Artus wrote:
On Friday, 16 August 2013 at 17:45:35 UTC, Suliman wrote:
On Friday, 16 August 2013 at 16:07:59 UTC, Andre Artus wrote:
I would like to contribute to the D ecosystem, but as I'm still
in the learning process I do not want to get my
On Friday, 16 August 2013 at 20:12:20 UTC, Jonathan M Davis wrote:
On Friday, August 16, 2013 21:57:01 Andre Artus wrote:
It is disheartening to think that the people with potential for
the most valuable contributions or insight will be avoiding
discussions regarding the documentation. But I
On 08/16/2013 01:38 PM, Meta wrote:
See Ali's thread in D.Learn about assigning a TypeTuple to an enum.
I think it was captaindet's enum and tuples thread that was
specifically about enum and TypeTuple:
http://forum.dlang.org/post/ku21fk$oqc$1...@digitalmars.com
Ali
On Fri, Aug 16, 2013 at 10:52:11PM +0200, Andre Artus wrote:
[...]
I just noticed when posting my previous reply to you that it
connected to an NNTP server (I normally context switch on anything
that takes more than a fraction of a second, so I have not seen it
before). So I guess that many
Awhile ago Kenji posted this excellent dip
(http://wiki.dlang.org/DIP32) that aimed to improve tuple syntax,
and described several cases in which tuples could be
destructured. You can see his original thread here:
On Friday, 16 August 2013 at 20:56:49 UTC, Ali Çehreli wrote:
On 08/16/2013 01:38 PM, Meta wrote:
See Ali's thread in D.Learn about assigning a TypeTuple to an
enum.
I think it was captaindet's enum and tuples thread that was
specifically about enum and TypeTuple:
On 08/16/2013 02:11 PM, Meta wrote:
On Friday, 16 August 2013 at 20:56:49 UTC, Ali Çehreli wrote:
I think it was captaindet's enum and tuples thread that was
specifically about enum and TypeTuple:
http://forum.dlang.org/post/ku21fk$oqc$1...@digitalmars.com
Ali
Ah, sorry, my mistake.
1 - 100 of 191 matches
Mail list logo