Re: Beta D 2.070.0-b1
On 01/03/2016 09:20 PM, tsbockman wrote: > > Any hope for this? > > https://github.com/D-Programming-Language/dmd/pull/3407#issuecomment-136974686 > > It's been bugging a lot of people lately. Well, this still needs a lot of work that nobody was did. Walter spend almost the whole release cycle on EH, I spend a huge amount of time on nightlies/install scripts and was away half of the cycle. So while I still think 313&314 should be one of our main priorities, it seems I couldn't convince anyone.
Re: Using D and std.ndslice as a Numpy Replacement
On 1/2/16 6:24 PM, Ilya Yaroshenko wrote:
On Saturday, 2 January 2016 at 23:23:38 UTC, Ilya Yaroshenko wrote:
On Saturday, 2 January 2016 at 19:49:05 UTC, Jack Stouffer wrote:
http://jackstouffer.com/blog/nd_slice.html
https://www.reddit.com/r/programming/comments/3z6f7a/using_d_and_stdndslice_as_a_numpy_replacement/
I just wanted to write to you that dip80-ndslice was moved to mir
http://code.dlang.org/packages/mir
"dependencies": {
"dip80-ndslice": "~>0.8.7"
},
Ilya
EDIT:
"dependencies": {
"mir": "~>0.9.0-beta"
}
What is the relationship between mir and std.experimental.ndslice? -- Andrei
Re: Better docs for D (WIP)
On 1/2/16 2:31 PM, JohnCK wrote: On Wednesday, 30 December 2015 at 23:05:11 UTC, Adam D. Ruppe wrote: This huge friction has killed my desire to contribute to Phobos before and it looks like it is again. the difference is this time, I have my own fork so the community doesn't have to lose out. Please keep the good work. The current documentation is a mess, but the "heads" can't see it. I have a lot a free time, I'd already pointed out the error links you gave on the other response, but in fact I'd like to fix by myself, but then I see how hard is the current process that I couldn't go with it. But currently I'm looking to your project and maybe I could help there. A few follow-up questions, all serious: Do the projected advantages of Adam's project do not include ease of contribution? If so, how? Would it be productive to reduce friction to contribute to the current two documentation systems we have, instead of coming with a third system that is likely to have its own issues? What are the exact difficulties of improving the documentation that you just cannot push past in spite of having time and willingness to contribute? Andrei
Re: Using D and std.ndslice as a Numpy Replacement
On Monday, 4 January 2016 at 01:09:30 UTC, Ilya wrote: To be clear: there is NO data in Article example. Only CPU registers are used. It is not fair. -- Ilya Ok, I see were I made the mistake, I apologize. I believed that since I was only testing the np.mean line of code, that the lazy generation of the D in the D version would have no effects on the comparison. But I forgot the fact that the lazy generation would mean that no memory needed to be accessed in the D code and therefore it's not apples to apples with the Numpy code. Thank you for clarifying this, I will update the article.
Re: Using D and std.ndslice as a Numpy Replacement
On Sunday, 3 January 2016 at 23:18:16 UTC, Andrei Alexandrescu
wrote:
On 1/2/16 6:24 PM, Ilya Yaroshenko wrote:
On Saturday, 2 January 2016 at 23:23:38 UTC, Ilya Yaroshenko
wrote:
On Saturday, 2 January 2016 at 19:49:05 UTC, Jack Stouffer
wrote:
http://jackstouffer.com/blog/nd_slice.html
https://www.reddit.com/r/programming/comments/3z6f7a/using_d_and_stdndslice_as_a_numpy_replacement/
I just wanted to write to you that dip80-ndslice was moved to
mir
http://code.dlang.org/packages/mir
"dependencies": {
"dip80-ndslice": "~>0.8.7"
},
Ilya
EDIT:
"dependencies": {
"mir": "~>0.9.0-beta"
}
What is the relationship between mir and
std.experimental.ndslice? -- Andrei
1. mir.ndslice is a developer version of std.experimental.ndslice
2. mir can be used with DMD front end >= 2.068, so ndslice can be
used with LDC 0.17.0-alpha. It is important for benchmarks.
3. mir is going to be a testing package for the future std.la
(generic BLAS implementation)
-- Ilya
Re: Beta D 2.070.0-b1
On Sunday, 3 January 2016 at 20:20:19 UTC, tsbockman wrote: On Sunday, 3 January 2016 at 19:24:57 UTC, Martin Nowak wrote: First beta for the 2.070.0 release. Any hope for this? https://github.com/D-Programming-Language/dmd/pull/3407#issuecomment-136974686 It's been bugging a lot of people lately. +1
Re: Beta D 2.070.0-b1
On Sunday, 3 January 2016 at 19:24:57 UTC, Martin Nowak wrote: First beta for the 2.070.0 release. Any hope for this? https://github.com/D-Programming-Language/dmd/pull/3407#issuecomment-136974686 It's been bugging a lot of people lately.
Re: Using D and std.ndslice as a Numpy Replacement
On Monday, 4 January 2016 at 00:24:51 UTC, David Nadlinger wrote: On Sunday, 3 January 2016 at 18:56:07 UTC, Jack Stouffer wrote: I still have to disagree with you that the example I submitted was fair. Accessing global memory in D is going to be much slower than accessing stack memory, […] What leads you to this belief? (Beyond cache locality considerations, which are not so important if the data is large.) The example in the article and the example I submitted to DlangScience/examples have very different speeds: https://github.com/DlangScience/examples/blob/master/mean_of_columns.d Article example: 5 µs DlangScience example: 145 µs Both when compiled with LDC
Re: Damage Control: An homage to Rampart (Alpha)
On Sunday, 3 January 2016 at 19:53:25 UTC, Ivan Kazmenko wrote: "If, at the end of a round, you have no territory, you are defeated." I'm almost sure this is currently not true for the last round: the "completed" message showed up for me instead of "defeated". Huh, I couldn't repro that. Maybe you had some territory you didn't notice? Right now even having a single tile enclosed counts -- which actually may be too lenient. Its also possible there's a bug in the detection of enclosed areas.
Re: DLanguage IntelliJ plugin released
On Friday, 1 January 2016 at 15:37:44 UTC, Minas Mina wrote: On Wednesday, 30 December 2015 at 17:17:07 UTC, Israel wrote: On Wednesday, 30 December 2015 at 17:04:15 UTC, Suliman wrote: On Monday, 28 December 2015 at 19:23:17 UTC, Kingsley wrote: On Friday, 25 December 2015 at 17:43:06 UTC, Kingsley wrote: On Friday, 25 December 2015 at 16:55:32 UTC, Bogdan wrote: [...] Raise any issues at the GitHub page and I will fix - I will write some documentation over the next few days also Intellij D plugin version 1.5 released with improved DUB support and bug fixes How to install this plugin on Windows? Intellij Idea 14 on windows. File > Settings > plugins > browse repositories The plugin does not show up on Intellij Idea 15 though so im guessing it isnt compatible yet and neither on CLion. I am actually using it with IntelliJ 15. I'm still on IntelliJ 14 so haven't tried it with 15 personally - but it should be fine. IT should work fine on windows as well - although I'm an OSX user so have only ever tested it on OSX - please raise any windows specific issues at the github project https://github.com/kingsleyh/DLanguage/issues At the moment I've restricted the plugin to Intellij - so it won't work on other jetbrains products - but It should not be hard to get it working on CLion.
Re: Hash Tables in D
On Sunday, 3 January 2016 at 19:29:05 UTC, Martin Nowak wrote: On 01/01/2016 04:27 PM, Minas Mina wrote: On Friday, 1 January 2016 at 13:59:35 UTC, Walter Bright wrote: http://minas-mina.com/2016/01/01/associative-arrays/ https://www.reddit.com/r/programming/comments/3z03ji/hash_tables_in_the_d_programming_language/ Thanks for sharing this. I am the author. :) There is a bug. You should never do this b/c of iterator/range invalidation. foreach (key; aa.keys) aa.remove(key); The reference states that keys: "Returns dynamic array, the elements of which are the keys in the associative array". Isn't the array newly allocated?
Re: Using D and std.ndslice as a Numpy Replacement
On Sunday, 3 January 2016 at 00:17:23 UTC, Ilya Yaroshenko wrote: On Sunday, 3 January 2016 at 00:09:33 UTC, Jack Stouffer wrote: On Saturday, 2 January 2016 at 23:51:09 UTC, Ilya Yaroshenko wrote: This benchmark is _not_ lazy, so ndslice faster than Numpy only 3.5 times. I don't know what you mean here, I made sure to call std.array.array to force allocation. In the article: auto means = 100_000.iota < 100_000.iota is lazy range .sliced(100, 1000) .transposed .map!(r => sum(r) / r.length) .array; < allocation of the result In GitHub: means = data < data is allocated array, it is fair test for real world .sliced(100, 1000) .transposed .map!(r => sum(r, 0L) / cast(double) r.length) .array; < allocation of the result -- Ilya I still have to disagree with you that the example I submitted was fair. Accessing global memory in D is going to be much slower than accessing stack memory, and sense most std.ndslice calculations are going to be on the stack, I believe my benchmark is indicative of normal use.
Re: Using D and std.ndslice as a Numpy Replacement
On Sunday, 3 January 2016 at 18:56:07 UTC, Jack Stouffer wrote: On Sunday, 3 January 2016 at 00:17:23 UTC, Ilya Yaroshenko wrote: [...] I still have to disagree with you that the example I submitted was fair. Accessing global memory in D is going to be much slower than accessing stack memory, and sense most std.ndslice calculations are going to be on the stack, I believe my benchmark is indicative of normal use. No, for real world math calculations, most std.ndslice will be at global memory. Examples: all SciD (if port it to ndslice), future BLAS, future LAPACK. -- Ilya
Re: Damage Control: An homage to Rampart (Alpha)
On Saturday, 2 January 2016 at 23:43:48 UTC, thedeemon wrote: On Thursday, 31 December 2015 at 16:43:53 UTC, rcorre wrote: It works fine for me on Win 8.1. But I have no idea what's going on in the game, gameplay is totally unknown to me. ;) I added some instructions on the readme: https://github.com/rcorre/damage_control#how-to-play However, I'm getting the impression that I need to include some better explanations in-game. I guess the gameplay only seemed obvious to me because I made it :) Thanks for trying it out!
Beta D 2.070.0-b1
First beta for the 2.070.0 release. Still a few things missing from the changelog, there is a new package std.experimental.ndslice, and native (DWARF based) exception handling on linux. http://dlang.org/download.html#dmd_beta http://dlang.org/changelog/2.070.0.html Please report any bugs at https://issues.dlang.org -Martin
Re: Hash Tables in D
On 01/01/2016 04:27 PM, Minas Mina wrote: > On Friday, 1 January 2016 at 13:59:35 UTC, Walter Bright wrote: >> http://minas-mina.com/2016/01/01/associative-arrays/ >> >> https://www.reddit.com/r/programming/comments/3z03ji/hash_tables_in_the_d_programming_language/ >> > > Thanks for sharing this. I am the author. :) There is a bug. You should never do this b/c of iterator/range invalidation. foreach (key; aa.keys) aa.remove(key);
Re: Beta D 2.070.0-b1
On Sunday, 3 January 2016 at 19:24:57 UTC, Martin Nowak wrote: First beta for the 2.070.0 release. Still a few things missing from the changelog, there is a new package std.experimental.ndslice, and native (DWARF based) exception handling on linux. http://dlang.org/download.html#dmd_beta http://dlang.org/changelog/2.070.0.html Please report any bugs at https://issues.dlang.org -Martin Thanks!
Re: Damage Control: An homage to Rampart (Alpha)
On Sunday, 3 January 2016 at 17:09:08 UTC, rcorre wrote: I added some instructions on the readme: https://github.com/rcorre/damage_control#how-to-play "If, at the end of a round, you have no territory, you are defeated." I'm almost sure this is currently not true for the last round: the "completed" message showed up for me instead of "defeated".
Re: Using D and std.ndslice as a Numpy Replacement
On Saturday, 2 January 2016 at 19:49:05 UTC, Jack Stouffer wrote: http://jackstouffer.com/blog/nd_slice.html https://www.reddit.com/r/programming/comments/3z6f7a/using_d_and_stdndslice_as_a_numpy_replacement/ Nicely written, good to see you explain all the code, enjoyed reading it.
