On 07-Jul-2015 21:41, Andrei Alexandrescu wrote:
Got a desk and an Internet connection, so I'm ready for anything.
Destroy!! -- Andrei
Would be awesome if you could review/approve/merge some of recent
dlang.org pulls especially ones tagged with spec.
Got a desk and an Internet connection, so I'm ready for anything.
Destroy!! -- Andrei
On Fri, 23 Nov 2012 07:40:25 -, Jacob Carlborg d...@me.com wrote:
On 2012-11-23 00:43, Jonathan M Davis wrote:
Or even more likely, no design documentation gets written at all...
Example, this post is not threaded correctly for me.
Nor for me (Opera 12.11 Win32 Windows7).
R
--
Using
On Fri, 23 Nov 2012 07:41:08 -, Jacob Carlborg d...@me.com wrote:
On 2012-11-23 05:07, H. S. Teoh wrote:
Or any documentation at all.
I recall, with a shudder, how one fine day a high-priority Javascript
project (high-priority as in, it was due the week before it was given to
me) was
On Thursday, 22 November 2012 at 16:05:10 UTC, H. S. Teoh wrote:
On Wed, Nov 21, 2012 at 10:10:51PM -0800, Jonathan M Davis
wrote:
On Friday, November 16, 2012 18:09:44 H. S. Teoh wrote:
On Fri, Nov 16, 2012 at 08:52:39PM -0500, Jonathan M Davis
wrote:
[...]
The problem is that supporting
What if we did it so that transient ranges would have to define
transient property (as was previously proposed), and
isInputRange, isForwardRange and others would get an additional
parameter allowTransient. The default value of that argument
would be false, so those templates would evaluate to
On Friday, November 23, 2012 16:34:51 jerro wrote:
What if we did it so that transient ranges would have to define
transient property (as was previously proposed), and
isInputRange, isForwardRange and others would get an additional
parameter allowTransient. The default value of that
On Friday, November 23, 2012 08:39:42 Jacob Carlborg wrote:
The threading is not fine on some of your posts in Thunderbird for me.
Well, I have no idea what the problem is, and there's nothing that I can do
about it. The inner workings of e-mail and newsgroup software are a mystery to
me.
-
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
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
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
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.
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
On Friday, November 16, 2012 18:09:44 H. S. Teoh wrote:
On Fri, Nov 16, 2012 at 08:52:39PM -0500, Jonathan M Davis wrote:
On Friday, November 16, 2012 13:55:31 H. S. Teoh wrote:
I don't like the prospect of having to duplicate parts of
std.algorithm just because I have some code that
On Wed, Nov 21, 2012 at 10:10:51PM -0800, Jonathan M Davis wrote:
On Friday, November 16, 2012 18:09:44 H. S. Teoh wrote:
On Fri, Nov 16, 2012 at 08:52:39PM -0500, Jonathan M Davis wrote:
[...]
The problem is that supporting transience complicates ranges even
further, and they're already
On 11/22/2012 8:07 AM, H. S. Teoh wrote:
On Wed, Nov 21, 2012 at 10:10:51PM -0800, Jonathan M Davis wrote:
On Friday, November 16, 2012 18:09:44 H. S. Teoh wrote:
The way you an Jonathan are replying is breaking the message threading model.
How are you doing it?
On Thursday, November 22, 2012 12:53:36 Walter Bright wrote:
On 11/22/2012 8:07 AM, H. S. Teoh wrote:
On Wed, Nov 21, 2012 at 10:10:51PM -0800, Jonathan M Davis wrote:
On Friday, November 16, 2012 18:09:44 H. S. Teoh wrote:
The way you an Jonathan are replying is breaking the message
On Thu, Nov 22, 2012 at 12:53:36PM -0800, Walter Bright wrote:
On 11/22/2012 8:07 AM, H. S. Teoh wrote:
On Wed, Nov 21, 2012 at 10:10:51PM -0800, Jonathan M Davis wrote:
On Friday, November 16, 2012 18:09:44 H. S. Teoh wrote:
The way you an Jonathan are replying is breaking the message
On Thursday, November 22, 2012 15:36:58 H. S. Teoh wrote:
In theory, software is implemented according to the design that has been
carefully worked out beforehand. In practice, design documents are
written after the fact to describe the sorry mess that has gone on
before.
Or even more likely,
On Thu, Nov 22, 2012 at 03:43:24PM -0800, Jonathan M Davis wrote:
On Thursday, November 22, 2012 15:36:58 H. S. Teoh wrote:
In theory, software is implemented according to the design that has
been carefully worked out beforehand. In practice, design documents
are written after the fact to
On 2012-11-22 22:18, Jonathan M Davis wrote:
It's threading just fine in my mail client. I do recall there being some issue
with newsgroup vs mailing list threading though. Maybe what you're seeing is
related to that.
The threading is not fine on some of your posts in Thunderbird for me.
--
On 2012-11-23 05:07, H. S. Teoh wrote:
Or any documentation at all.
I recall, with a shudder, how one fine day a high-priority Javascript
project (high-priority as in, it was due the week before it was given to
me) was dumped on my lap, consisting of a non-trivial class hierarchy
and bunch of
On 2012-11-23 00:43, Jonathan M Davis wrote:
Or even more likely, no design documentation gets written at all...
Example, this post is not threaded correctly for me.
--
/Jacob Carlborg
Andrei Alexandrescu wrote:
Hi all,
I'm back from a few long trips during which I got behind reading this
group. I decided to mark everything as read and restart anew. If there
are any topics that you believe have extinguished but need my
attention, I'd be indebted if you mentioned them
On 11/16/2012 01:58 AM, Jonathan M Davis wrote:
On Thursday, November 15, 2012 22:11:33 Timon Gehr wrote:
On 11/14/2012 08:32 PM, Jonathan M Davis wrote:
On Wednesday, November 14, 2012 20:18:26 Timon Gehr wrote:
That is a very imprecise approximation. I think it does not cover any
ground:
On Friday, November 16, 2012 19:06:05 Timon Gehr wrote:
The suggestion is to ban all potentially mutable indirections from
'non-transient' ranges. (this redefines what 'transient' means.) It
cannot be derived that popFront will invalidate stuff just from the fact
that the type system does not
On Fri, Nov 16, 2012 at 10:32:22PM +0100, Jonathan M Davis wrote:
[...]
Regardless, std.array.array _cannot_ work on ranges with transient
fronts. So, we have a few options:
1. Make transient fronts illegal, then std.array.array and its ilk
never have to worry about it.
2. Make it so that
On Friday, November 16, 2012 13:55:31 H. S. Teoh wrote:
I don't like the prospect of
having to duplicate parts of std.algorithm just because I have some code
that produces transient ranges -- I *know* I'm never going to need to
use algorithms on them that can't handle transience anyway. It's
On Fri, Nov 16, 2012 at 08:52:39PM -0500, Jonathan M Davis wrote:
On Friday, November 16, 2012 13:55:31 H. S. Teoh wrote:
I don't like the prospect of having to duplicate parts of
std.algorithm just because I have some code that produces transient
ranges -- I *know* I'm never going to need
Andrei Alexandrescu seewebsiteforem...@erdani.org wrote in message
news:k81k6s$1qm7$1...@digitalmars.com...
On 11/14/12 5:30 PM, Daniel Murphy wrote:
Andrei Alexandrescuseewebsiteforem...@erdani.org wrote in message
news:k80l8p$397$1...@digitalmars.com...
On 11/14/12 7:29 AM, H. S. Teoh
On Thursday, November 15, 2012 22:07:22 Daniel Murphy wrote:
Is that really good enough? Keeping ranges simple is important, but so is
making the obvious solution 'just work'.
std.array.array will never work with ranges with a transient front unless it
somehow knew when it was and wasn't
std.array.array will never work with ranges with a transient
front unless it
somehow knew when it was and wasn't appropriate to dup, which
it's not going
to know purely by looking at the type of front. The creator of
the range would
have to tell them somehow. And even then, it wouldn't work
On Thursday, November 15, 2012 13:17:12 jerro wrote:
std.array.array will never work with ranges with a transient
front unless it
somehow knew when it was and wasn't appropriate to dup, which
it's not going
to know purely by looking at the type of front. The creator of
the range would
On Wed, 2012-11-14 at 18:31 -0800, Andrei Alexandrescu wrote:
array(map!a.dup(stdin.byLine()))
As it seems there is a good way of handling ranges with transient front
for algorithms that need a persistent front?
Why not simply document any transient range to be transient (should be
anyway) and
On Thursday, 15 November 2012 at 12:57:24 UTC, Jonathan M Davis
wrote:
It's looking like this comes down to either banning ranges with
transient
fronts entirely (and changing how ByLine and ByChunk work), or
we're going to
have to deal with quirks like array(map!a.dup(file.byLine()))
not
11/15/2012 5:20 PM, monarch_dodra пишет:
On Thursday, 15 November 2012 at 12:57:24 UTC, Jonathan M Davis wrote:
It's looking like this comes down to either banning ranges with transient
fronts entirely (and changing how ByLine and ByChunk work), or we're
going to
have to deal with quirks like
On Thu, Nov 15, 2012 at 04:38:04AM -0800, Jonathan M Davis wrote:
On Thursday, November 15, 2012 13:17:12 jerro wrote:
std.array.array will never work with ranges with a transient front
unless it somehow knew when it was and wasn't appropriate to dup,
which it's not going to know purely
On Thu, Nov 15, 2012 at 02:14:15PM +0100, eskimo wrote:
On Wed, 2012-11-14 at 18:31 -0800, Andrei Alexandrescu wrote:
array(map!a.dup(stdin.byLine()))
As it seems there is a good way of handling ranges with transient
front for algorithms that need a persistent front?
Why not simply
On 11/14/2012 08:32 PM, Jonathan M Davis wrote:
On Wednesday, November 14, 2012 20:18:26 Timon Gehr wrote:
That is a very imprecise approximation. I think it does not cover any
ground: The day eg. 'array' will require this kind of non-transient
element range is the day where I will write my
On 11/14/2012 11:18 PM, Andrei Alexandrescu wrote:
On 11/14/12 11:18 AM, Timon Gehr wrote:
On 11/14/2012 06:43 PM, Andrei Alexandrescu wrote:
On 11/14/12 7:29 AM, H. S. Teoh wrote:
But since this isn't going to be fixed properly, then the only solution
left is to arbitrarily declare transient
On Thursday, November 15, 2012 22:11:33 Timon Gehr wrote:
On 11/14/2012 08:32 PM, Jonathan M Davis wrote:
On Wednesday, November 14, 2012 20:18:26 Timon Gehr wrote:
That is a very imprecise approximation. I think it does not cover any
ground: The day eg. 'array' will require this kind of
On Thu, 2012-11-15 at 10:56 -0800, H. S. Teoh wrote:
I don't like duplicating a whole bunch of algorithms in
transalgorithm.
If its true what you say, that usually there is no difference in
efficiency, than there is no need for any duplication. But it is
certainly better to offer an standard
On Wed, Nov 14, 2012 at 12:51:45AM +0100, deadalnix wrote:
Le 13/11/2012 20:13, Jonathan M Davis a écrit :
On Tuesday, November 13, 2012 09:45:17 H. S. Teoh wrote:
Unfortunately, using ranges in their most general sense is looking
like a pipe dream to me right now, and I'm ready to just move
On 11/14/12 7:29 AM, H. S. Teoh wrote:
But since this isn't going to be fixed properly, then the only solution
left is to arbitrarily declare transient ranges as not ranges (even
though the concept of ranges itself has no such implication, and many
algorithms don't even need such assumptions),
On 11/14/2012 06:43 PM, Andrei Alexandrescu wrote:
On 11/14/12 7:29 AM, H. S. Teoh wrote:
But since this isn't going to be fixed properly, then the only solution
left is to arbitrarily declare transient ranges as not ranges (even
though the concept of ranges itself has no such implication, and
On Wednesday, November 14, 2012 20:18:26 Timon Gehr wrote:
That is a very imprecise approximation. I think it does not cover any
ground: The day eg. 'array' will require this kind of non-transient
element range is the day where I will write my own.
std.array.array _cannot_ work with a
On Wednesday, November 14, 2012 07:29:34 H. S. Teoh wrote:
On Wed, Nov 14, 2012 at 12:51:45AM +0100, deadalnix wrote:
Le 13/11/2012 20:13, Jonathan M Davis a écrit :
On Tuesday, November 13, 2012 09:45:17 H. S. Teoh wrote:
Unfortunately, using ranges in their most general sense is looking
On 11/14/12 11:18 AM, Timon Gehr wrote:
On 11/14/2012 06:43 PM, Andrei Alexandrescu wrote:
On 11/14/12 7:29 AM, H. S. Teoh wrote:
But since this isn't going to be fixed properly, then the only solution
left is to arbitrarily declare transient ranges as not ranges (even
though the concept of
Andrei Alexandrescu seewebsiteforem...@erdani.org wrote in message
news:k80l8p$397$1...@digitalmars.com...
On 11/14/12 7:29 AM, H. S. Teoh wrote:
But since this isn't going to be fixed properly, then the only solution
left is to arbitrarily declare transient ranges as not ranges (even
though
On 11/14/12 5:30 PM, Daniel Murphy wrote:
Andrei Alexandrescuseewebsiteforem...@erdani.org wrote in message
news:k80l8p$397$1...@digitalmars.com...
On 11/14/12 7:29 AM, H. S. Teoh wrote:
But since this isn't going to be fixed properly, then the only solution
left is to arbitrarily declare
Le 13/11/2012 03:59, Andrei Alexandrescu a écrit :
On 11/12/12 6:29 PM, deadalnix wrote:
Le 13/11/2012 03:01, Andrei Alexandrescu a écrit :
On 11/12/12 5:40 PM, deadalnix wrote:
I never used moveFront and alike.
They're used by algorithms that you might be using.
Andrei
I'm not saying
Andrei Alexandrescu wrote:
Hi all,
I'm back from a few long trips during which I got behind reading this
group. I decided to mark everything as read and restart anew. If there
are any topics that you believe have extinguished but need my
attention, I'd be indebted if you mentioned them
Andrei Alexandrescu wrote:
I'm leaning toward doing nothing about this.
Translated: I am looking forwad to retirrment. Or, I am so burnt ot but
you stupid sheeple actually believe what I say, I am not tired, I am a
liar.
Andrei Alexandrescu wrote:
Hi all,
I'm back from a few long trips during which I got behind reading this
group. I decided to mark everything as read and restart anew. If there
are any topics that you believe have extinguished but need my
attention, I'd be indebted if you mentioned them
On 11/12/2012 11:09 PM, bearophile wrote:
In this thread
http://forum.dlang.org/thread/50a0eea4.7010...@webdrake.net
Joseph Rushton Wakeling suggests code like this to compile:
struct Foo(_T) {
alias _T T;
}
void bar(FooT)(FooT foo, FooT.T x) {
}
void main() {
Foo!int foo;
Joseph Rushton Wakeling:
I'm not actually suggesting that the particular syntax above
necessarily ought to work, but I'd like an easy way to ensure
that one template parameter can be determined from another.
Right. But I think that syntax is the most natural one for that.
And Hara now
On 11/13/2012 03:01 PM, bearophile wrote:
Right. But I think that syntax is the most natural one for that.
Agree. :-)
And Hara now thinks it's an idea worth considering:
http://d.puremagic.com/issues/show_bug.cgi?id=9004#c3
Excellent! Thank you so much for bringing it to notice like this.
On Mon, Nov 12, 2012 at 03:57:42PM -0800, Andrei Alexandrescu wrote:
On 11/12/12 3:14 PM, Jonathan M Davis wrote:
On Monday, November 12, 2012 12:28:14 Andrei Alexandrescu wrote:
Topic on range transience probably, as it is
almost concluded.
I'm leaning toward doing nothing about this.
On Tuesday, November 13, 2012 09:45:17 H. S. Teoh wrote:
Unfortunately, using ranges in their most general sense
is looking like a pipe dream to me right now, and I'm ready to just move
on.
The reality of the matter is that there are limits to any abstraction. In
order to make it take more
On Tuesday, 13 November 2012 at 10:53:49 UTC, Job wrote:
Oh yes, likely see about revising the forum to allow either
attaching/moving a post to an appropriate location, or allow a
flagging system where we can remove spam posts like from Job...
To do that, likely needs multiple votes, so
Le 13/11/2012 20:13, Jonathan M Davis a écrit :
On Tuesday, November 13, 2012 09:45:17 H. S. Teoh wrote:
Unfortunately, using ranges in their most general sense
is looking like a pipe dream to me right now, and I'm ready to just move
on.
The reality of the matter is that there are limits to
On 12-11-2012 20:42, Andrei Alexandrescu wrote:
Hi all,
I'm back from a few long trips during which I got behind reading this
group. I decided to mark everything as read and restart anew. If there
are any topics that you believe have extinguished but need my
attention, I'd be indebted if you
Hi all,
I'm back from a few long trips during which I got behind reading this
group. I decided to mark everything as read and restart anew. If there
are any topics that you believe have extinguished but need my
attention, I'd be indebted if you mentioned them to me via private email
Le 12/11/2012 20:42, Andrei Alexandrescu a écrit :
Hi all,
I'm back from a few long trips during which I got behind reading this
group. I decided to mark everything as read and restart anew. If there
are any topics that you believe have extinguished but need my
attention, I'd be indebted
On Monday, 12 November 2012 at 19:42:14 UTC, Andrei Alexandrescu
wrote:
Hi all,
I'm back from a few long trips during which I got behind
reading this group. I decided to mark everything as read and
restart anew. If there are any topics that you believe have
extinguished but need my
On 11/12/12 11:45 AM, deadalnix wrote:
Le 12/11/2012 20:42, Andrei Alexandrescu a écrit :
Hi all,
I'm back from a few long trips during which I got behind reading this
group. I decided to mark everything as read and restart anew. If there
are any topics that you believe have extinguished
On Monday, November 12, 2012 21:24:06 Rob T wrote:
Long discussion on const ref,
http://forum.dlang.org/thread/yhnbcocwxnbutylfe...@forum.dlang.org
here's the summary thread
http://forum.dlang.org/thread/zteryxwxyngvyqvuk...@forum.dlang.org
Yeah. You have some very strong views and that
On 2012-11-12 21:28, Andrei Alexandrescu wrote:
* I saw very little focus for attribute testing, i.e. does symbol xyz
have attribute abc? I don't think we should relegate that to a __traits.
The current implementation only has __traits(getAttributes), which will
basically return a tuple of
On Mon, Nov 12, 2012 at 2:28 PM, Andrei Alexandrescu
seewebsiteforem...@erdani.org wrote:
* The execution of that feature (merging in the trunk along with a bunch of
unrelated work) was extremely poor. We need to acquire a sense of urgency
about fixing our process, lest this mom-and-pop-shop
On 11/12/12 12:50 PM, Jacob Carlborg wrote:
What's also being discussed in addition to your points are:
* Should built in types be allowed as attributes
* Should only types explicitly marked as an attribute (somehow) be
allowed as attributes
Saw that too. I don't have an opinion about such,
On Mon, Nov 12, 2012 at 12:28:14PM -0800, Andrei Alexandrescu wrote:
On 11/12/12 11:45 AM, deadalnix wrote:
[...]
Topic on range transience probably, as it is almost concluded.
I'm leaning toward doing nothing about this.
[...]
Please don't. This is an issue that *needs* to be addressed, one
On Monday, November 12, 2012 12:28:14 Andrei Alexandrescu wrote:
Topic on range transience probably, as it is
almost concluded.
I'm leaning toward doing nothing about this.
As it stands, most everything assumes that front is not transient. But then we
have ByLine and ByChunk. So, they
On 11/12/12 3:14 PM, Jonathan M Davis wrote:
On Monday, November 12, 2012 12:28:14 Andrei Alexandrescu wrote:
Topic on range transience probably, as it is
almost concluded.
I'm leaning toward doing nothing about this.
As it stands, most everything assumes that front is not transient. But
Le 13/11/2012 00:57, Andrei Alexandrescu a écrit :
On 11/12/12 3:14 PM, Jonathan M Davis wrote:
On Monday, November 12, 2012 12:28:14 Andrei Alexandrescu wrote:
Topic on range transience probably, as it is
almost concluded.
I'm leaning toward doing nothing about this.
As it stands, most
On Monday, November 12, 2012 15:57:42 Andrei Alexandrescu wrote:
Here are two thoughts:
1. The notion of this is an input range that is not a forward range,
AND the element type has mutable indirections so it's not a proper value
type is a very close approximation of transiency. We could
On Monday, 12 November 2012 at 20:54:39 UTC, Jonathan M Davis
wrote:
On Monday, November 12, 2012 21:24:06 Rob T wrote:
Long discussion on const ref,
http://forum.dlang.org/thread/yhnbcocwxnbutylfe...@forum.dlang.org
here's the summary thread
Le 13/11/2012 01:57, Jonathan M Davis a écrit :
On Monday, November 12, 2012 15:57:42 Andrei Alexandrescu wrote:
Here are two thoughts:
1. The notion of this is an input range that is not a forward range,
AND the element type has mutable indirections so it's not a proper value
type is a very
On 11/12/12 5:40 PM, deadalnix wrote:
I never used moveFront and alike.
They're used by algorithms that you might be using.
Andrei
Le 13/11/2012 03:01, Andrei Alexandrescu a écrit :
On 11/12/12 5:40 PM, deadalnix wrote:
I never used moveFront and alike.
They're used by algorithms that you might be using.
Andrei
I'm not saying they are useless, or that I never used them under the hood.
On 11/12/12 6:29 PM, deadalnix wrote:
Le 13/11/2012 03:01, Andrei Alexandrescu a écrit :
On 11/12/12 5:40 PM, deadalnix wrote:
I never used moveFront and alike.
They're used by algorithms that you might be using.
Andrei
I'm not saying they are useless, or that I never used them under the
BCS Wrote:
Hello Joel,
PPS: Riot is looking for some strong senior engineers (3years+
experienced) so if your looking for work you may check out
www.riotgames.com.
Well I'm in the market, but I rater suspect that I don't have enough
experience
(~3 year, but none in that domain).
On 2/4/2010 3:55 PM, BCS wrote:
Hello Joel,
PPS: Riot is looking for some strong senior engineers (3years+
experienced) so if your looking for work you may check out
www.riotgames.com.
Well I'm in the market, but I rater suspect that I don't have enough
experience (~3 year, but none in that
I imagine a lot of people here don't remember me when I left a few years ago
to focus on a free game called league of legends (www.leagueoflegends.com).
Its been released however we're still working on making it even better.
Just out of curiosity, what's the business model? Is there in-game
On Thu, 04 Feb 2010 14:29:41 +0300, Bill Baxter wbax...@gmail.com wrote:
I imagine a lot of people here don't remember me when I left a few
years ago
to focus on a free game called league of legends
(www.leagueoflegends.com).
Its been released however we're still working on making it even
Hello Joel,
PPS: Riot is looking for some strong senior engineers (3years+
experienced) so if your looking for work you may check out
www.riotgames.com.
Well I'm in the market, but I rater suspect that I don't have enough experience
(~3 year, but none in that domain). Oh, well. (OTOH if
Hello,
Just wanted to congratulate Walter and the community for keeping D going
strong for so long. Its nice to see some features such as pure and
ranges have actually become realities. D 2.0 feels like its no-longer a
sibling language of D 1.0.
I imagine a lot of people here don't
86 matches
Mail list logo
