Re: Sociomantic

2014-03-19 Thread Mengu
On Tuesday, 18 March 2014 at 16:06:41 UTC, Sociomantic wrote: http://translate.google.com/translate?sl=de&tl=en&js=n&prev=_t&hl=en&ie=UTF-8&u=http%3A%2F%2Fwww.welt.de%2Fwirtschaft%2Fwebwelt%2Farticle125913260%2FBriten-kaufen-Berliner-Start-up-fuer-200-Millionen.html damn. was gonna apply for

Re: 1st draft of complete class-based std.random successor

2014-03-19 Thread Chris Williams
On Wednesday, 19 March 2014 at 23:49:41 UTC, Joseph Rushton Wakeling wrote: Hello all, As some of you may already know, monarch_dodra and I have spent quite a lot of time over the last year discussing the state of std.random. To cut a long story short, there are significant problems that ari

Re: 1st draft of complete class-based std.random successor

2014-03-19 Thread bearophile
Joseph Rushton Wakeling: Thanks for pointing me to the bug report; I'd forgotten that this was an open issue :-) In Bugzilla probably there are many bug reports/enhancement requests about std.random, so I suggest you to read them. Some of them can be useful, while other are probably already

Re: 1st draft of complete class-based std.random successor

2014-03-19 Thread Rikki Cattermole
On Thursday, 20 March 2014 at 00:15:22 UTC, Joseph Rushton Wakeling wrote: On Thursday, 20 March 2014 at 00:05:20 UTC, Joseph Rushton Wakeling wrote: Not really. There's still usable functionality in there for all architectures (although I'm not sure how practically useful). Just to expand o

Re: 1st draft of complete class-based std.random successor

2014-03-19 Thread Joseph Rushton Wakeling
On Thursday, 20 March 2014 at 00:39:43 UTC, bearophile wrote: Note: I meant a simple but very fast function that generates just one value in [0.0, 1.0] (not a range). There will be both. :-) Off the top of my head I'm not sure whether the interval will be [0.0, 1.0], [0.0, 1.0) or whether it

Re: 1st draft of complete class-based std.random successor

2014-03-19 Thread bearophile
Joseph Rushton Wakeling: No, but it's planned. Jerro wrote quite a nice one in the course of his work on the Ziggurat algorithm, and I'm sure he'd be happy for me to adapt it accordingly. Note: I meant a simple but very fast function that generates just one value in [0.0, 1.0] (not a range)

Re: 1st draft of complete class-based std.random successor

2014-03-19 Thread Joseph Rushton Wakeling
On Thursday, 20 March 2014 at 00:09:51 UTC, bearophile wrote: Please don't use stuttering names like "std.random2.randomShuffle". "std.random2.shuffle" is enough. I don't object to rewriting the names if there's a valid case for it, but it does seem to me to be important to try and match as m

Re: 1st draft of complete class-based std.random successor

2014-03-19 Thread Joseph Rushton Wakeling
On Thursday, 20 March 2014 at 00:09:51 UTC, bearophile wrote: Do you have a simple but very fast function that generates uniforms in [0.0, 1.0]? :-) No, but it's planned. Jerro wrote quite a nice one in the course of his work on the Ziggurat algorithm, and I'm sure he'd be happy for me to ad

Re: 1st draft of complete class-based std.random successor

2014-03-19 Thread Joseph Rushton Wakeling
On Thursday, 20 March 2014 at 00:05:20 UTC, Joseph Rushton Wakeling wrote: Not really. There's still usable functionality in there for all architectures (although I'm not sure how practically useful). Just to expand on that remark: my impression is that individual random devices are inevitab

Re: 1st draft of complete class-based std.random successor

2014-03-19 Thread Joseph Rushton Wakeling
On Wednesday, 19 March 2014 at 23:58:36 UTC, Rikki Cattermole wrote: Out of interest but, shouldn't in the device module have a static assert(0, "Not implemented yet") type of deal with the version(Posix) block? Not really. There's still usable functionality in there for all architectures (a

Re: 1st draft of complete class-based std.random successor

2014-03-19 Thread bearophile
Joseph Rushton Wakeling: Few first comments: * std.random2.adaptor, random "adaptors" such as randomShuffle, randomSample, etc. Please don't use stuttering names like "std.random2.randomShuffle". "std.random2.shuffle" is enough. My own feeling is that ultimately it is a responsib

Re: 1st draft of complete class-based std.random successor

2014-03-19 Thread Rikki Cattermole
Out of interest but, shouldn't in the device module have a static assert(0, "Not implemented yet") type of deal with the version(Posix) block?

1st draft of complete class-based std.random successor

2014-03-19 Thread Joseph Rushton Wakeling
Hello all, As some of you may already know, monarch_dodra and I have spent quite a lot of time over the last year discussing the state of std.random. To cut a long story short, there are significant problems that arise because the current RNGs are value types rather than reference types. We

Re: Dconf Hotel?

2014-03-19 Thread Steven Schveighoffer
On Tue, 18 Mar 2014 21:50:09 -0400, Mike Parker wrote: On 3/19/2014 7:56 AM, Steven Schveighoffer wrote: On Sat, 15 Mar 2014 17:59:26 -0400, Vladimir Panteleev wrote: Just to be clear, we're talking about this, right? http://www.aloftsiliconvalley.com/ Yep, that is where we gathered af

Re: Dconf Hotel?

2014-03-19 Thread Iain Buclaw
On 22 February 2014 03:23, Manu wrote: > On 22 February 2014 01:22, Steven Schveighoffer wrote: >> >> Last year, at the conference, after the sessions everyone met up at the >> Aloft hotel near Facebook's HQ to have passionate and fruitful discussions >> about D and I think a lot of good came out