On 17/09/2010 17:44, Andrei Alexandrescu wrote:
On 9/17/10 10:48 CDT, Michel Fortin wrote:
In my mind it's simpler to just explain the notion that an uninitialized
hash is null and detached from anything else until initialized. Objects
works like this (minus the implicit initialization part), so
On 09/27/2010 09:15 AM, Emil Madsen wrote:
Is there a partly complete release? - that just basic stuff available?
Latest trunk: http://bitbucket.org/qtd/repo
Wiki: http://www.dsource.org/projects/qtd
I have a local branch that should fix a couple of major problems but it
is not ready for a co
Is there a partly complete release? - that just basic stuff available?
On 26 September 2010 19:04, Max Samukha wrote:
> On 09/26/2010 05:36 PM, Emil Madsen wrote:
>
>> Just curious about QtD, how far did the design process go in terms of %
>> before it got suspended?
>> 10% - 25% - 50%? - and wh
On 09/26/2010 05:36 PM, Emil Madsen wrote:
Just curious about QtD, how far did the design process go in terms of %
before it got suspended?
10% - 25% - 50%? - and what would the time approximations be to finish it?
On 16 September 2010 16:22, Max Samukha mailto:spam...@d-coding.com>> wrote:
Just curious about QtD, how far did the design process go in terms of %
before it got suspended?
10% - 25% - 50%? - and what would the time approximations be to finish it?
On 16 September 2010 16:22, Max Samukha wrote:
> After a good amount of hesitation, we have decided to put the QtD project
>
On 09/17/2010 07:37 PM, Lutger wrote:
Georg Wrede wrote:
I take it this is directed at me. Look, it was a gut reaction. I don't
understand why, but if anyone takes offense I'm sorry, I didn't want to provoke
that.
I don't see why anybody should take offense from what you said. Quite
the oppos
On 2010-09-17 21:08:29 -0400, Walter Bright said:
Andrei Alexandrescu wrote:
On 9/17/10 10:48 CDT, Michel Fortin wrote:
I understand the intent quite well. I'm talking about what happens if
the source is const?
The whole point is, mutation is the motivator. If you copy an empty
hash, no pr
Andrei Alexandrescu wrote:
On 9/17/10 10:48 CDT, Michel Fortin wrote:
I understand the intent quite well. I'm talking about what happens if
the source is const?
The whole point is, mutation is the motivator. If you copy an empty
hash, no problem because the receiver can't mutate it.
Wouldn'
On 9/17/10 12:04 CDT, Steven Schveighoffer wrote:
On Fri, 17 Sep 2010 12:44:30 -0400, Andrei Alexandrescu
wrote:
On 9/17/10 10:48 CDT, Michel Fortin wrote:
I understand the intent quite well. I'm talking about what happens if
the source is const?
The whole point is, mutation is the motivato
On Fri, 17 Sep 2010 12:44:30 -0400, Andrei Alexandrescu
wrote:
On 9/17/10 10:48 CDT, Michel Fortin wrote:
I understand the intent quite well. I'm talking about what happens if
the source is const?
The whole point is, mutation is the motivator. If you copy an empty
hash, no problem becaus
On Fri, 17 Sep 2010 12:39:06 -0400, Andrei Alexandrescu
wrote:
On 09/17/2010 09:02 AM, Max Samukha wrote:
One example is the semantics of clear() and scoped(). As I understood
from one of your posts, you agree that resurrecting the destroyed object
by calling its default constructor is obj
On 9/17/10 10:48 CDT, Michel Fortin wrote:
I understand the intent quite well. I'm talking about what happens if
the source is const?
The whole point is, mutation is the motivator. If you copy an empty
hash, no problem because the receiver can't mutate it.
In my mind it's simpler to just ex
On 09/17/2010 09:02 AM, Max Samukha wrote:
On 09/17/2010 11:15 AM, Andrei Alexandrescu wrote:
Nice to hear that the problem is being worked on. What kind of
typechecking will be performed in const/immutable postblit?
The tricky part in that constructor is that you must be able to assign
the fi
Georg Wrede wrote:
> On 09/17/2010 01:01 AM, Lutger wrote:
>> Max Samukha wrote:
>>
>>> After a good amount of hesitation, we have decided to put the QtD
>>> project on hold. QtD has a potential to become a complete and effective
>>> development platform for D but it is not going to happen soon (u
On 09/17/2010 06:48 PM, Michel Fortin wrote:
On 2010-09-17 11:14:21 -0400, Andrei Alexandrescu
said:
Now that I think of it, you don't need a fancy struct to make this
problem appear, you just need two layers of functions:
void fun(const(int[int]) hash) {
fun(hash); // calling ourself, how can
On 2010-09-17 11:14:21 -0400, Andrei Alexandrescu
said:
On 9/17/10 9:18 CDT, Michel Fortin wrote:
On 2010-09-17 04:15:31 -0400, Andrei Alexandrescu
said:
On a funny note, we figured that for a number of reasons it would help
to allow C++-style constructors that offer access to the source;
On 9/17/10 9:18 CDT, Michel Fortin wrote:
On 2010-09-17 04:15:31 -0400, Andrei Alexandrescu
said:
On a funny note, we figured that for a number of reasons it would help
to allow C++-style constructors that offer access to the source; it
just turns out some idioms need to modify the source as w
On 2010-09-17 04:15:31 -0400, Andrei Alexandrescu
said:
On a funny note, we figured that for a number of reasons it would help
to allow C++-style constructors that offer access to the source; it
just turns out some idioms need to modify the source as well as the
destination.
One obvious ex
On 09/17/2010 11:15 AM, Andrei Alexandrescu wrote:
Thanks for replying. This is very helpful. I'll make some points below,
definitely not as an attempt to revisit the decision you've already made.
The recent big one is the unspecified behavior of
postblit on const/immutable structs and overloa
On 9/16/10 14:37 CDT, Max Samukha wrote:
On 09/16/2010 06:44 PM, Andrei Alexandrescu wrote:
On 9/16/10 9:22 CDT, Max Samukha wrote:
After a good amount of hesitation, we have decided to put the QtD
project on hold. QtD has a potential to become a complete and effective
development platform for
On 9/16/10 18:48 CDT, Georg Wrede wrote:
On 09/17/2010 01:01 AM, Lutger wrote:
Max Samukha wrote:
After a good amount of hesitation, we have decided to put the QtD
project on hold. QtD has a potential to become a complete and effective
development platform for D but it is not going to happen s
On 09/17/2010 01:01 AM, Lutger wrote:
Max Samukha wrote:
After a good amount of hesitation, we have decided to put the QtD
project on hold. QtD has a potential to become a complete and effective
development platform for D but it is not going to happen soon (unless
people with harder hearts take
On 9/17/10 12:25 AM, Lutger wrote:
Is the most recent flavor of QtD the repositoy at bitbucket?
Yes, it is. Reminds me that someone should probably update the Wiki page
at dsource…
Is the most recent flavor of QtD the repositoy at bitbucket?
Max Samukha wrote:
> After a good amount of hesitation, we have decided to put the QtD
> project on hold. QtD has a potential to become a complete and effective
> development platform for D but it is not going to happen soon (unless
> people with harder hearts take it over). We have spent half of
On 09/16/2010 06:44 PM, Andrei Alexandrescu wrote:
On 9/16/10 9:22 CDT, Max Samukha wrote:
After a good amount of hesitation, we have decided to put the QtD
project on hold. QtD has a potential to become a complete and effective
development platform for D but it is not going to happen soon (unle
On 9/16/10 9:22 CDT, Max Samukha wrote:
After a good amount of hesitation, we have decided to put the QtD
project on hold. QtD has a potential to become a complete and effective
development platform for D but it is not going to happen soon (unless
people with harder hearts take it over). We have
After a good amount of hesitation, we have decided to put the QtD
project on hold. QtD has a potential to become a complete and effective
development platform for D but it is not going to happen soon (unless
people with harder hearts take it over). We have spent half of the day
hunting yet anot
28 matches
Mail list logo
