Front-end release.NEXT (page 2)

August 30, 2013

Re: Front-end release.NEXT

Posted by H. S. Teoh

Permalink

H. S. Teoh

Permalink

On Fri, Aug 30, 2013 at 08:00:35PM +0100, Iain Buclaw wrote:
> On Aug 30, 2013 7:34 PM, "H. S. Teoh" <hsteoh@quickfur.ath.cx> wrote:
> >
> > On Fri, Aug 30, 2013 at 03:41:34PM +0200, Iain Buclaw wrote: [...]
> > > Across D/Druntime/Phobos, there are currently 26 open major bugs
> > > since 28/05/2013.
> > > http://bit.ly/173WrZf
> > >
> > > 18 open critical bugs.
> > > http://bit.ly/16WkhcM
> > >
> > > 5 blockers.
> > > http://bit.ly/18q1pkC
> > >
> > > And 14 regressions.
> > > http://bit.ly/15pLzVb
> > [...]
> >
> > I obtained a +1 Sword of Bisection from a git this morning, and decided to go commit hunting. I found the specific commits that introduced the following regressions (see bug notes for the offending commits):
> >
> > 10687 - Refused cast from uint[] to array of uint-based enums at
> compile-time
> > 10401 - ICE(ztc/symbol.c 1035) - inline Nullable struct with JSONValue
> > 10425 - Link error with templates
> > 10555 - enumerator can no longer increment beyond maximum of initializer
> > 10617 - contract with -profile -debug is not nothrow
> > 10630 - Structs with disabled default construction can't be used as `out`
> parameters
> >
> > I would fix them myself, except that my dmd-fu level isn't high enough to take them on yet. ;-)
> >
> 
> Thanks, I take it you linked in the specific commits in the bug reports?  I can have a look later and chime in, however bugs that don't affect me won't get reviewed.  :)
[...]

Well, I posted the SHA hashes... I didn't think to actually link to the github URL. That's an excellent idea; I'll keep that in mind next time. In any case, it shouldn't be too hard to find the code on github with the SHA hashes. Or better yet, just git checkout <hash>. :)


T

-- 
"Life is all a great joke, but only the brave ever get the point." -- Kenneth Rexroth

On Fri, Aug 30, 2013 at 12:05:12PM -0700, Adam Wilson wrote: [...] > I don't know how much action D is going to be getting next week due to Walter's attendance of GoingNative, but IIRC last year Walter was able to sneak in a commit or two... Looks like Andrei is going to be a speaker there as well, so Phobos fixes might be a bit slow as well (though we have a team of other committers who could alleviate that). > This would actually be a good opportunity for the community to have pulls fixing the Criticals/Blockers/Regressions waiting for Walter when he gets back from GoingNative. Might make getting a new release that much smoother and sooner. :-) [...] And have them all green and ready to merge by the time he gets back -- the autotester appears to be experiencing load problems recently, so it would be nice to give it some time to catch up on all the pulls. It should make the next release happen sooner... but I'm not sure about smoother, though. A higher rate of code changes usually means more potential regressions with the associated chaos that follows thereafter. :) T -- Heads I win, tails you lose.

On 30 August 2013 20:19, H. S. Teoh <hsteoh@quickfur.ath.cx> wrote: > On Fri, Aug 30, 2013 at 12:05:12PM -0700, Adam Wilson wrote: [...] >> I don't know how much action D is going to be getting next week due to Walter's attendance of GoingNative, but IIRC last year Walter was able to sneak in a commit or two... > > Looks like Andrei is going to be a speaker there as well, so Phobos fixes might be a bit slow as well (though we have a team of other committers who could alleviate that). > Hopefully in a year's time, the release process for D and Phobos should have a bigger bus factor than 1 (each). The core developers surrounding both D and Phobos are certainly self supporting without too much weight being put onto two (highly distinguished) gentlemen. :o) -- Iain Buclaw *(p < e ? p++ : p) = (c & 0x0f) + '0';

On 8/30/2013 11:32 AM, H. S. Teoh wrote: > On Fri, Aug 30, 2013 at 03:41:34PM +0200, Iain Buclaw wrote: > [...] >> Across D/Druntime/Phobos, there are currently 26 open major bugs >> since 28/05/2013. >> http://bit.ly/173WrZf >> >> 18 open critical bugs. >> http://bit.ly/16WkhcM >> >> 5 blockers. >> http://bit.ly/18q1pkC >> >> And 14 regressions. >> http://bit.ly/15pLzVb > [...] > > I obtained a +1 Sword of Bisection from a git this morning, and decided > to go commit hunting. I found the specific commits that introduced the > following regressions (see bug notes for the offending commits): > > 10687 - Refused cast from uint[] to array of uint-based enums at compile-time > 10401 - ICE(ztc/symbol.c 1035) - inline Nullable struct with JSONValue > 10425 - Link error with templates > 10555 - enumerator can no longer increment beyond maximum of initializer > 10617 - contract with -profile -debug is not nothrow > 10630 - Structs with disabled default construction can't be used as `out` parameters > > I would fix them myself, except that my dmd-fu level isn't high enough > to take them on yet. ;-) Thank you. This is great information.

On 8/30/2013 12:05 PM, Adam Wilson wrote: > I don't know how much action D is going to be getting next week due to Walter's > attendance of GoingNative, but IIRC last year Walter was able to sneak in a > commit or two... The GoingNative is a great conference, and if the past is any guide, they'll be all day & evening and I'll be barely able to answer any emergency emails let alone get any work done for those days. I won't be bringing my laptop.

On 8/30/2013 6:41 AM, Iain Buclaw wrote: > Morning all, > > It has been about 3 months since the last release of the D front-end > implementation. Three years experience and carrying out over 100 merges into > GDC tells me that each time the development cycle starts edging towards it's > fourth month, it makes things an absolute nightmare, in both the time consumed > merging in the changes, and with time spent tracking down bug reports for > unittests/testsuite cases that test backend code generation - with 2.060, 2.061 > and 2.063 being the worst releases I have ever had to deal with - before 2.060 > the release schedule (if it even qualifies as a 'schedule') was anywhere between > 1-2 months. > > So I would want to give everyone on the dev team a kick and get the alpha/beta > out the door. > > Across D/Druntime/Phobos, there are currently 26 open major bugs since 28/05/2013. > http://bit.ly/173WrZf > > 18 open critical bugs. > http://bit.ly/16WkhcM > > 5 blockers. > http://bit.ly/18q1pkC > > And 14 regressions. > http://bit.ly/15pLzVb I think it's a good idea. The only further enhancement I really want to get in this release is DLL support for Linux.

On 2013-08-30 21:50, Walter Bright wrote: > I think it's a good idea. > > The only further enhancement I really want to get in this release is DLL > support for Linux. Do you mean loading DLL's completely at runtime, i.e. using dlopen? We have already shipped Phobos as a DLL. -- /Jacob Carlborg

On 8/30/13, Walter Bright <newshound2@digitalmars.com> wrote: > The only further enhancement I really want to get in this release is DLL support for Linux. And if it's (mostly) done, we should put it in the changelog, since it's a pretty big deal!

On Saturday, 31 August 2013 at 11:24:41 UTC, Jacob Carlborg wrote: > Do you mean loading DLL's completely at runtime, i.e. using dlopen? We have already shipped Phobos as a DLL. Yep, see https://github.com/D-Programming-Language/druntime/pull/593 and linked pull requests. David

Forums