> It's not worth the extra complication. Every algorithm ever written then has
> to worry about it (though clearly many outside of Phobos wouldn't bother), and
> it's yet another thing that anyone writing a range-based function has to take
> into account. Any function which doesn't take it into account will then end up
> with wrong and bizarre behavior when it's given a range with a transient
> front.

My proposal was that for example isInputRange!R wouldn't compile if R was transient. So as long as people used the existing is***Range templates, the code that called an algorithm that only works with non-transient ranges with a transient range wouldn't compile. The functions that do support transient ranges could check for isInputRange!(R, true) instead of checking for isInputRange!R.

> To be correct, most range-based functions would have to add template
> constraints to block ranges which mark themselves as transient.

If they already use is***Range constraints, they wouldn't have to add anything.

On 11/22/2012 06:36 PM, H. S. Teoh wrote:
>
> The threading is fine in my MUA (mutt); I think somebody mentioned some
> time ago that Mailman is inserting/substituting message IDs where it
> shouldn't, which causes things to break. I'm not sure exactly what or
> where, though.

Yes, it is the "puremagic" mail-to-news gateway. Here's the explanation for the last time this problem was discussed:

http://forum.dlang.org/post/jo2c5s$f1$1@digitalmars.com

It's about time to "fix it or fuck it" with Mailman.

On Friday, November 23, 2012 22:13:17 jerro wrote:
> > It's not worth the extra complication. Every algorithm ever
> > written then has
> > to worry about it (though clearly many outside of Phobos
> > wouldn't bother), and
> > it's yet another thing that anyone writing a range-based
> > function has to take
> > into account. Any function which doesn't take it into account
> > will then end up
> > with wrong and bizarre behavior when it's given a range with a
> > transient
> > front.
> 
> My proposal was that for example isInputRange!R wouldn't compile if R was transient. So as long as people used the existing is***Range templates, the code that called an algorithm that only works with non-transient ranges with a transient range wouldn't compile. The functions that do support transient ranges could check for isInputRange!(R, true) instead of checking for isInputRange!R.
> 
> > To be correct, most range-based functions would have to add
> > template
> > constraints to block ranges which mark themselves as transient.
> 
> If they already use is***Range constraints, they wouldn't have to add anything.

So, isInputRange wouldn't compile with any range which declared an enum which marked it as transient? If a range doesn't pass isInputRange, then it isn't a range in the first place, and it's likely to cause problems if something passes isInputRange under some circumstances and not others. Not to mention, trying to add a second argument to isInputRange just complicates things.

And regardless of what kind of constraint is used or whether any needs to be added, the fact that such a range might exist complicates any and every range which is written. Every range must either ignore the possibility of a range being transient, or it has to code for it. If much of anything ignores transient ranges, then there was no point in having them in the first place. And anything which doesn't ignore them just got more complicated.

It's just not worth it.

- Jonathan M Davis

On Friday, 23 November 2012 at 21:37:54 UTC, Jeff Nowakowski wrote:
> On 11/22/2012 06:36 PM, H. S. Teoh wrote:
>>
>> The threading is fine in my MUA (mutt); I think somebody mentioned some
>> time ago that Mailman is inserting/substituting message IDs where it
>> shouldn't, which causes things to break. I'm not sure exactly what or
>> where, though.
>
> Yes, it is the "puremagic" mail-to-news gateway. Here's the explanation for the last time this problem was discussed:
>
> http://forum.dlang.org/post/jo2c5s$f1$1@digitalmars.com
>
> It's about time to "fix it or fuck it" with Mailman.

I know how to work around this problem (subscribe to both the mailing list and newsgroup, and store both Message-IDs). I just need to allocate some time to work on the forum again. Hopefully around the end of the month.

On Friday, 23 November 2012 at 21:42:02 UTC, Vladimir Panteleev wrote:
>> Yes, it is the "puremagic" mail-to-news gateway. Here's the explanation for the last time this problem was discussed:
>>
>> http://forum.dlang.org/post/jo2c5s$f1$1@digitalmars.com
>>
>> It's about time to "fix it or fuck it" with Mailman.
>
> I know how to work around this problem (subscribe to both the mailing list and newsgroup, and store both Message-IDs). I just need to allocate some time to work on the forum again. Hopefully around the end of the month.

Sorry, I assumed you were talking about the forum specifically :) Obviously the above applies only to forum users.

On Fri, Nov 23, 2012 at 06:26:52PM +0100, David Nadlinger wrote:
> On Friday, 23 November 2012 at 17:24:30 UTC, H. S. Teoh wrote:
> >What about something based off my povray D-man model?
> 
> D-man? Seriously? ;)
[...]

Why not? Java had Duke, so D has D-Man. :)


T

-- 
Caffeine underflow. Brain dumped.

On 11/23/2012 04:46 PM, Vladimir Panteleev wrote:
>>
>> I know how to work around this problem (subscribe to both the mailing
>> list and newsgroup, and store both Message-IDs). I just need to
>> allocate some time to work on the forum again. Hopefully around the
>> end of the month.
>
> Sorry, I assumed you were talking about the forum specifically :)
> Obviously the above applies only to forum users.

Right. The problem needs to be dealt with at the Mailman gateway for newsgroup users.