Now that that one is fixed, can we roll out a beta?

On 13 September 2010 19:07, David Simcha <dsimcha at gmail.com> wrote:
> Here be a showstopper Phobos regression related to Zip plus sort.? IMHO we should not release until this is fixed.
>
> http://d.puremagic.com/issues/show_bug.cgi?id=4861
>
> _______________________________________________
> phobos mailing list
> phobos at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/phobos
>

Sounds good.

Andrei

On 09/13/2010 06:43 PM, Don Clugston wrote:
> Now that that one is fixed, can we roll out a beta?
>
> On 13 September 2010 19:07, David Simcha<dsimcha at gmail.com>  wrote:
>> Here be a showstopper Phobos regression related to Zip plus sort.  IMHO we should not release until this is fixed.
>>
>> http://d.puremagic.com/issues/show_bug.cgi?id=4861
>>
>> _______________________________________________
>> phobos mailing list
>> phobos at puremagic.com
>> http://lists.puremagic.com/mailman/listinfo/phobos
>>
> _______________________________________________
> phobos mailing list
> phobos at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/phobos

<Poke>Walter</Poke>

You've been conspicuously absent from this thread so far.

On Mon, 13 Sep 2010, Andrei Alexandrescu wrote:

> Date: Mon, 13 Sep 2010 18:47:08 -0500
> From: Andrei Alexandrescu <andrei at erdani.com>
> Reply-To: Discuss the phobos library for D <phobos at puremagic.com>
> To: Discuss the phobos library for D <phobos at puremagic.com>
> Subject: Re: [phobos] next release
> 
> Sounds good.
> 
> Andrei
> 
> On 09/13/2010 06:43 PM, Don Clugston wrote:
> > Now that that one is fixed, can we roll out a beta?
> > 

I'm working on it. It'll help if people stop checking in things unless critical! Otherwise, my testing is perpetually out of sync.

Brad Roberts wrote:
> <Poke>Walter</Poke>
>
> You've been conspicuously absent from this thread so far.
>
> On Mon, 13 Sep 2010, Andrei Alexandrescu wrote:
>
> 
>> Date: Mon, 13 Sep 2010 18:47:08 -0500
>> From: Andrei Alexandrescu <andrei at erdani.com>
>> Reply-To: Discuss the phobos library for D <phobos at puremagic.com>
>> To: Discuss the phobos library for D <phobos at puremagic.com>
>> Subject: Re: [phobos] next release
>>
>> Sounds good.
>>
>> Andrei
>>
>> On 09/13/2010 06:43 PM, Don Clugston wrote:
>> 
>>> Now that that one is fixed, can we roll out a beta?
>>>
>>> 
> _______________________________________________
> phobos mailing list
> phobos at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/phobos
>
>
> 

Rats. I was on a roll fixing simple bugs assigned to me, in chronological order. I'm stopping at changeset 1999.

Thanks,

Andrei

On 09/13/2010 10:29 PM, Walter Bright wrote:
> I'm working on it. It'll help if people stop checking in things unless critical! Otherwise, my testing is perpetually out of sync.
>
> Brad Roberts wrote:
>> <Poke>Walter</Poke>
>>
>> You've been conspicuously absent from this thread so far.
>>
>> On Mon, 13 Sep 2010, Andrei Alexandrescu wrote:
>>
>>> Date: Mon, 13 Sep 2010 18:47:08 -0500
>>> From: Andrei Alexandrescu <andrei at erdani.com>
>>> Reply-To: Discuss the phobos library for D <phobos at puremagic.com>
>>> To: Discuss the phobos library for D <phobos at puremagic.com>
>>> Subject: Re: [phobos] next release
>>>
>>> Sounds good.
>>>
>>> Andrei
>>>
>>> On 09/13/2010 06:43 PM, Don Clugston wrote:
>>>> Now that that one is fixed, can we roll out a beta?
>>>>
>> _______________________________________________
>> phobos mailing list
>> phobos at puremagic.com
>> http://lists.puremagic.com/mailman/listinfo/phobos
>>
>>
> _______________________________________________
> phobos mailing list
> phobos at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/phobos

Well.. it'd help if you chimed in with any sort of agreement or plans.  Without any communication, why should anyone have paused their work?

Sigh,
Brad

On 9/13/2010 8:29 PM, Walter Bright wrote:
> I'm working on it. It'll help if people stop checking in things unless critical! Otherwise, my testing is perpetually out of sync.
> 
> Brad Roberts wrote:
>> <Poke>Walter</Poke>
>>
>> You've been conspicuously absent from this thread so far.
>>
>> On Mon, 13 Sep 2010, Andrei Alexandrescu wrote:
>>
>> 
>>> Date: Mon, 13 Sep 2010 18:47:08 -0500
>>> From: Andrei Alexandrescu <andrei at erdani.com>
>>> Reply-To: Discuss the phobos library for D <phobos at puremagic.com>
>>> To: Discuss the phobos library for D <phobos at puremagic.com>
>>> Subject: Re: [phobos] next release
>>>
>>> Sounds good.
>>>
>>> Andrei
>>>
>>> On 09/13/2010 06:43 PM, Don Clugston wrote:
>>> 
>>>> Now that that one is fixed, can we roll out a beta?
>>>>
>>>> 
>> _______________________________________________
>> phobos mailing list
>> phobos at puremagic.com
>> http://lists.puremagic.com/mailman/listinfo/phobos
>>
>>
>> 
> _______________________________________________
> phobos mailing list
> phobos at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/phobos

  BTW, is this release going to be fully capable of 64-bit semantic
analysis so we can start fixing libraries for when code gen is done?

On 9/13/2010 11:29 PM, Walter Bright wrote:
> I'm working on it. It'll help if people stop checking in things unless critical! Otherwise, my testing is perpetually out of sync.
>
> Brad Roberts wrote:
>> <Poke>Walter</Poke>
>>
>> You've been conspicuously absent from this thread so far.
>>
>> On Mon, 13 Sep 2010, Andrei Alexandrescu wrote:
>>
>>> Date: Mon, 13 Sep 2010 18:47:08 -0500
>>> From: Andrei Alexandrescu <andrei at erdani.com>
>>> Reply-To: Discuss the phobos library for D <phobos at puremagic.com>
>>> To: Discuss the phobos library for D <phobos at puremagic.com>
>>> Subject: Re: [phobos] next release
>>>
>>> Sounds good.
>>>
>>> Andrei
>>>
>>> On 09/13/2010 06:43 PM, Don Clugston wrote:
>>>> Now that that one is fixed, can we roll out a beta?
>>>>
>> _______________________________________________
>> phobos mailing list
>> phobos at puremagic.com
>> http://lists.puremagic.com/mailman/listinfo/phobos
>>
>>
> _______________________________________________
> phobos mailing list
> phobos at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/phobos
>

David Simcha wrote:
>  BTW, is this release going to be fully capable of 64-bit semantic
> analysis so we can start fixing libraries for when code gen is done?
>

Yes.

On Sep 9, 2010, at 5:25 PM, Jonathan M Davis wrote:
> 
> Just so you know, I fully expect that the datetime code that I've been working on will be done in less than a month. It'll be at least a week (probably closer to two), but it certainly won't be in the range of a month. Now, how many changes will be required after it's reviewed, or whether it will be accepted at all, is another matter. But it shouldn't be all that much longer before I'm done.

There are a bunch of routines in druntime that could really use a structured timespan representation (Boost actually even uses a full SystemTime class for most of these) and I'm trying to work out the best way to do this.  In Tango, the decision was to have the routines all accept a long value that is the same resolution as the tick count from TimeSpan, which is why everything currently works as it does.  I've always hated this and would love to do something more structured, but complications arise from possible redundancy or incompatibility with std.time.  What I've done for now is duplicate Boost's time_duration struct (as TimeDuration) into core.time, and I'm looking at using this for Thread.sleep(), etc.  Thoughts?

On Thursday, September 16, 2010 15:39:19 Sean Kelly wrote:
> On Sep 9, 2010, at 5:25 PM, Jonathan M Davis wrote:
> > Just so you know, I fully expect that the datetime code that I've been working on will be done in less than a month. It'll be at least a week (probably closer to two), but it certainly won't be in the range of a month. Now, how many changes will be required after it's reviewed, or whether it will be accepted at all, is another matter. But it shouldn't be all that much longer before I'm done.
> 
> There are a bunch of routines in druntime that could really use a
> structured timespan representation (Boost actually even uses a full
> SystemTime class for most of these) and I'm trying to work out the best
> way to do this.  In Tango, the decision was to have the routines all
> accept a long value that is the same resolution as the tick count from
> TimeSpan, which is why everything currently works as it does.  I've always
> hated this and would love to do something more structured, but
> complications arise from possible redundancy or incompatibility with
> std.time.  What I've done for now is duplicate Boost's time_duration
> struct (as TimeDuration) into core.time, and I'm looking at using this for
> Thread.sleep(), etc.  Thoughts?
> _______________________________________________
> phobos mailing list
> phobos at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/phobos

For what I've done, I have an enum of possible time units : year, month, week, day, hour, second, minute, second, millisecond, microsecond,  and tick (where a tick is 100 nanoseconds). I then have a Duration struct which is templatized on the time unit enum and takes a value. So, you end up with a Duration which which has a value (which is a long) and a type of time unit (e.g. 10 seconds or 1000 days). All of the functions that take a Duration are templatized so they will take any Duration with units that they're compatible with (the main problem with making them compatible with _all_ time units being that you cannot convert between years or months and any other units without a specific date because the number of days in a month is not consistent).

How all that would be applied to core.time, I don't know. I'd have to look at what it's doing.

- Jonathan M Davis