Re: Developer positions at Sociomantic Labs
On Monday, 12 June 2017 at 16:54:09 UTC, Joseph Rushton Wakeling wrote: Hello all, I'm happy to announce that we have some new D developer positions on offer at Sociomantic: https://www.sociomantic.com/jobs/d-software-developer-adserving/ https://www.sociomantic.com/jobs/software-developer-d-language-bidding/ The first of these would particularly suit someone with experience with statistics, data science, and/or machine learning. For the second, we're looking for someone with a good solid UNIX background (fully capable of going down all the twisty dark rabbit holes and finding those pesky hard-to-catch rabbits), preferably also with a good understanding of internet protocols. D experience is nice, but by no means necessary: a capable C/C++ background is just fine. Hope to hear from some of you soon :-) All the best, -- Joe 唉、、My poor English、、、
Re: Revised DIP Info
On Monday, 12 June 2017 at 17:51:05 UTC, Mike Parker wrote: Now that I've got a few DIP reviews under my belt, I've got a good enough handle on the process to lay it out in documentation form. To that end [1], I've kept the general structure that Dicebot initially set down, changing the details to better reflect my view of how it should all work (I still need to update the existing DIPs to reflect a couple of changes). I've also revised Dicebot's guidelines on DIP writing [2]. Much of his original advice is still there. That document is sure to evolve. Feedback on all of this is welcome. While I have your attention, Sebastian recently revived an old DIP on in-place struct initialization. I invite everyone to come and give feedback on that [3], but *please* read the updated README before doing so, particularly the section titled 'Review Process' so you can fully understand what's expected of reviews at this stage of the process (what I now call the 'Draft Review' stage). I haven't looked at it yet, but I expect to do so next week. I still need to review the recent updates to Zach Tollen's proposal [4] (Improve Contract Usability), and if all checks out I'll be merging it as DIP 1009. You can expect the first review round shortly thereafter. [1] https://github.com/dlang/DIPs/blob/master/README.md [2] https://github.com/dlang/DIPs/blob/master/GUIDELINES.md [3] https://github.com/dlang/DIPs/pull/71 [4] https://github.com/dlang/DIPs/pull/66 The guidelines should also contain some advice on check whether there's already a similar idea proposed. I wanted to write my own about how we should fix the DLL issue under Windows, only to find out that DIP45 already exists.
Re: LDC 1.3.0-beta2
On Monday, 12 June 2017 at 17:49:46 UTC, kinke wrote: LDC 1.3.0-beta2, the LLVM-based D compiler, is available for download! This release is based on the 2.073.2 frontend and standard library and supports LLVM 3.5-4.0. A snap package for this, using the LLVM 4.0.0 backend, is available in the 1.3/beta release channel. New users can install this with: sudo snap install --classic --channel=1.3/beta ldc2 while existing users can switch to it with sudo snap refresh --classic --channel=1.3/beta ldc2
Re: LDC 1.3.0-beta2
On Monday, 12 June 2017 at 17:49:46 UTC, kinke wrote: Hi everyone, LDC 1.3.0-beta2, the LLVM-based D compiler, is available for download! This release is based on the 2.073.2 frontend and standard library and supports LLVM 3.5-4.0. It's been a while since beta1, so besides numerous fixes there are also new features. Change log and downloads: https://github.com/ldc-developers/ldc/releases/tag/v1.3.0-beta2 Regards, kinke Nice job. Its good to see LLVM support progressing.
Revised DIP Info
Now that I've got a few DIP reviews under my belt, I've got a good enough handle on the process to lay it out in documentation form. To that end [1], I've kept the general structure that Dicebot initially set down, changing the details to better reflect my view of how it should all work (I still need to update the existing DIPs to reflect a couple of changes). I've also revised Dicebot's guidelines on DIP writing [2]. Much of his original advice is still there. That document is sure to evolve. Feedback on all of this is welcome. While I have your attention, Sebastian recently revived an old DIP on in-place struct initialization. I invite everyone to come and give feedback on that [3], but *please* read the updated README before doing so, particularly the section titled 'Review Process' so you can fully understand what's expected of reviews at this stage of the process (what I now call the 'Draft Review' stage). I haven't looked at it yet, but I expect to do so next week. I still need to review the recent updates to Zach Tollen's proposal [4] (Improve Contract Usability), and if all checks out I'll be merging it as DIP 1009. You can expect the first review round shortly thereafter. [1] https://github.com/dlang/DIPs/blob/master/README.md [2] https://github.com/dlang/DIPs/blob/master/GUIDELINES.md [3] https://github.com/dlang/DIPs/pull/71 [4] https://github.com/dlang/DIPs/pull/66
LDC 1.3.0-beta2
Hi everyone, LDC 1.3.0-beta2, the LLVM-based D compiler, is available for download! This release is based on the 2.073.2 frontend and standard library and supports LLVM 3.5-4.0. It's been a while since beta1, so besides numerous fixes there are also new features. Change log and downloads: https://github.com/ldc-developers/ldc/releases/tag/v1.3.0-beta2 Regards, kinke
Developer positions at Sociomantic Labs
Hello all, I'm happy to announce that we have some new D developer positions on offer at Sociomantic: https://www.sociomantic.com/jobs/d-software-developer-adserving/ https://www.sociomantic.com/jobs/software-developer-d-language-bidding/ The first of these would particularly suit someone with experience with statistics, data science, and/or machine learning. For the second, we're looking for someone with a good solid UNIX background (fully capable of going down all the twisty dark rabbit holes and finding those pesky hard-to-catch rabbits), preferably also with a good understanding of internet protocols. D experience is nice, but by no means necessary: a capable C/C++ background is just fine. Hope to hear from some of you soon :-) All the best, -- Joe
Re: Generalized Linear Models and Stochastic Gradient Descent in D
On Monday, 12 June 2017 at 14:46:30 UTC, jmh530 wrote: On Sunday, 11 June 2017 at 15:57:14 UTC, Ilya wrote: [...] Thanks. This will definitely be a very useful library. Your write-up might explain the meaning of the name. Laeeth proposed the name https://en.wikipedia.org/wiki/L%C3%BCbeck Also, as you haven't done the announce yet, I'm still a little unsure about how high level Lubeck will get. For instance, if I write some Matrix math heavy code, then it's going to have mtimes all throughout it. I think there was some discussion in the past about a struct with opBinary overloaded (at which point it may be useful to point out that a DIP to add some more things that opBinary could overload might be useful). Yes, the DIP for opBinary would be very useful.
Re: Generalized Linear Models and Stochastic Gradient Descent in D
On Sunday, 11 June 2017 at 15:57:14 UTC, Ilya wrote: It uses mir-blas and mir-lapack packages. They are low level and satisfy betterC requirements. Mir is a libraries collection to write more high level easy to use libraries. Mir should provide basic data types, patterns, and low level API. Lubeck is high level library for scripting like programming. I like that it is located at Kaleidic GitHub. It is very important for D to have successful open source commercial projects. mir-blas, mir-lapack, and Lubeck are sponsored by Symmetry Investments and Kaleidic Associates. Another example is ASDF by Tamedia Digital. BTW, I need to write announce ) Thanks. This will definitely be a very useful library. Your write-up might explain the meaning of the name. Also, as you haven't done the announce yet, I'm still a little unsure about how high level Lubeck will get. For instance, if I write some Matrix math heavy code, then it's going to have mtimes all throughout it. I think there was some discussion in the past about a struct with opBinary overloaded (at which point it may be useful to point out that a DIP to add some more things that opBinary could overload might be useful).
