Re: D IDE Coedit - version 3 beta 3

On Friday, 27 January 2017 at 04:48:56 UTC, Basile B. wrote: This would probably have been a RC or even the final version if I hadn't to wait for the development platform I use to reach its next milestone, which may not happen before the next spring, so another beta is worth. All important

Re: two points

On Thursday, 9 February 2017 at 17:45:15 UTC, Nick Sabalausky wrote: No. There should be appropriate checks and reviews, yes. But, no, every little fix and improvement shouldn't feel like trying to get somewhere in a year-long tabs vs spaces debate or making a big-budget sales pitch to

Re: Questionnaire

On Thursday, 9 February 2017 at 17:28:47 UTC, jmh530 wrote: I would probably say libraries is most important. Mir is a great advance. I've been applauding your work all the way through. There are two things that I think Mir needs most (and we've talked about them before as things you were

Re: two points

On 2/9/2017 1:45 PM, Jon Degenhardt wrote: However, when a PR associated with the issue is created, the ticket itself is normally not updated until after the review is finished and the PR closed, to late to help out. It normally is. I do it for all mine and for others I notice that have not

Re: two points

On 2/9/2017 1:06 PM, Joseph Rushton Wakeling wrote: On Thursday, 9 February 2017 at 20:43:00 UTC, Walter Bright wrote: *Anyone* in this community can step up and do that. Anyone can make observations and proposals, but not everyone has the authority to effect change. Anyone can proactively

Re: two points

On Thursday, 9 February 2017 at 16:48:16 UTC, Joseph Rushton Wakeling wrote: There's clearly in part a scaling problem here (in terms of how many people are available in general, and in terms of how many people have expertise on particular parts of the library) but it also feels like a few

Re: two points

On Thursday, 9 February 2017 at 20:43:00 UTC, Walter Bright wrote: *Anyone* in this community can step up and do that. Anyone can make observations and proposals, but not everyone has the authority to effect change. I appreciate how frustrating it must be to have people saying, 'Hey, do

Re: two points

On Thursday, 9 February 2017 at 16:48:16 UTC, Joseph Rushton Wakeling wrote: which is that after some initial interest and feedback, the PR just got left alone with no decision to accept or reject it, and no indication of why. This is why I only contribute to Phobos to be quite honest. I

Re: two points

Dne 9.2.2017 v 21:43 Walter Bright via Digitalmars-d-announce napsal(a): On 2/9/2017 12:29 PM, Joseph Rushton Wakeling wrote: Yes, but it could be good to examine what can be done to more pro-actively look at open PRs that have had no recent follow-up. *Anyone* in this community can step up

Re: two points

On 2/9/2017 12:29 PM, Joseph Rushton Wakeling wrote: Yes, but it could be good to examine what can be done to more pro-actively look at open PRs that have had no recent follow-up. *Anyone* in this community can step up and do that.

Re: two points

On Thursday, 9 February 2017 at 19:53:37 UTC, Walter Bright wrote: There's a lot going on needing attention, and sometimes a bit of championing is needed by their proponents. Yes, but it could be good to examine what can be done to more pro-actively look at open PRs that have had no recent

Re: two points

On Thursday, 9 February 2017 at 19:58:57 UTC, Seb wrote: We gave this a try a couple of months ago with Facebook's mention-bot: Example: https://github.com/dlang/phobos/pull/4318#issuecomment-241817191 Repo: https://github.com/dlang-bots/mention-bot Eventually I disabled it because people

Re: two points

On Thursday, 9 February 2017 at 19:42:03 UTC, Jack Stouffer wrote: On Thursday, 9 February 2017 at 19:36:52 UTC, Walter Bright wrote: Good idea! Please investigate how to get github to generate such emails. In the meantime, the PR guidelines are here: We gave this a try a couple of months ago

Re: two points

On 2/9/2017 8:55 AM, Joseph Rushton Wakeling wrote: On Thursday, 9 February 2017 at 09:49:53 UTC, Walter Bright wrote: In any case, shouldn't it be an uphill battle to merge things? There are a lot of things that need to be satisfied to merge something. Being too hasty leads to legacy code that

Re: two points

On Thursday, 9 February 2017 at 19:36:52 UTC, Walter Bright wrote: Good idea! Please investigate how to get github to generate such emails. In the meantime, the PR guidelines are here: This is already somewhat done with the PR bot we have. The DlangBot notifies reviewers on the DMD repo, but

Re: vibe.d 0.8.0 and 0.7.31 beta releases

Am 09.02.2017 um 18:00 schrieb Kagamin: On Wednesday, 8 February 2017 at 15:18:34 UTC, Sönke Ludwig wrote: The problem is that there are two affected call stacks - the @system API function that registers the @system callback, wrapping/casting it as @trusted, and the event handler that later on

Re: two points

On 2/9/2017 8:48 AM, Joseph Rushton Wakeling wrote: Contrast this with the experience I had the one time I submitted a (tiny, trivial) patch to rust: immediately after submitting the PR I got a message from their 'highfive' robot that included: * a friendly thank you for the PR; * the

Re: Questionnaire

On Thursday, 9 February 2017 at 18:38:32 UTC, John Colvin wrote: On Thursday, 9 February 2017 at 18:34:44 UTC, bachmeier wrote: On Thursday, 9 February 2017 at 17:28:47 UTC, jmh530 wrote: Other stuff I would find useful: 1) R integration (I know someone's done work on this, but it's hard to

Re: Questionnaire

On Thursday, 9 February 2017 at 18:34:44 UTC, bachmeier wrote: On Thursday, 9 February 2017 at 17:28:47 UTC, jmh530 wrote: Other stuff I would find useful: 1) R integration (I know someone's done work on this, but it's hard to find and I don't remember if it works on Windows. Really just

Re: Questionnaire

On Thursday, 9 February 2017 at 17:28:47 UTC, jmh530 wrote: Other stuff I would find useful: 1) R integration (I know someone's done work on this, but it's hard to find and I don't remember if it works on Windows. Really just needs a champion) Me. The latest version is here:

Re: two points

On 02/09/2017 04:49 AM, Walter Bright wrote: On 2/8/2017 11:09 PM, Nick Sabalausky wrote: And any PRs I have managed to get through were all uphill battles the whole way. You have contributed 5 PRs to dmd: https://github.com/dlang/dmd/pulls?q=is%3Apr+author%3Aabscissa 1 is open

Re: Questionnaire

On Thursday, 9 February 2017 at 16:33:18 UTC, bachmeier wrote: Make extensions that others can use within their current workflow, and they will use it. Leave it as a Dub package and they won't touch it. You've done a lot of good work, but it's kind of a dead end to target the standalone D

Re: Questionnaire

On Wednesday, 8 February 2017 at 18:27:57 UTC, Ilya Yaroshenko wrote: 1. Why your company uses D? a. D is the best b. We like D c. I like D and my company allowed me to use D d. My head like D e. Because marketing reasons f. Because my company can be more efficient with D for some

Updated LDC snap package with link-time optimization (LTO) support

Revision 3 of the ldc2 snap package is now available in the 'edge' channel of the snap store. This still provides LDC 1.1.0, but with the following important changes: * the backend is provided by LLVM 3.9.1 * support for LDC's experimental link-time optimization (the

Re: vibe.d 0.8.0 and 0.7.31 beta releases

On Wednesday, 8 February 2017 at 15:18:34 UTC, Sönke Ludwig wrote: The problem is that there are two affected call stacks - the @system API function that registers the @system callback, wrapping/casting it as @trusted, and the event handler that later on actually calls the callback. The latter

Re: two points

On Thursday, 9 February 2017 at 09:49:53 UTC, Walter Bright wrote: In any case, shouldn't it be an uphill battle to merge things? There are a lot of things that need to be satisfied to merge something. Being too hasty leads to legacy code that we come to regret, angry people whose code was

Re: two points

On Thursday, 9 February 2017 at 08:02:23 UTC, Walter Bright wrote: The PR in question: https://github.com/dlang/dmd/pull/4745 It took me a while to find it, because you were using a pseudonym that I did not recognize. There are a number of frequent contributors to D using pseudonyms, and

Game Website Server Side

Hello All! We have a multiplayer game website which uses D programming language for server side instant interactions. I need someone professional who is able to make some changes on request. We are the company and we will allocate money for these tasks. It is not only one time task , we are

Re: Questionnaire

On Wednesday, 8 February 2017 at 18:27:57 UTC, Ilya Yaroshenko wrote: 2. Have you use one of the following Mir projects in production: a. https://github.com/libmir/mir b. https://github.com/libmir/mir-algorithm c. https://github.com/libmir/mir-cpuid d.

Re: Questionnaire

On Wednesday, 8 February 2017 at 18:27:57 UTC, Ilya Yaroshenko wrote: 1. Why your company uses D? a. D is the best b. We like D c. I like D and my company allowed me to use D d. My head like D e. Because marketing reasons f. Because my company can be more efficient with D for some

Re: two points

On Thursday, 9 February 2017 at 08:02:23 UTC, Walter Bright wrote: I suppose I could write a cheat sheet and tape it to the wall of my office, but why not just use your name? It shouldn't matter who wrote it. Review the code, not the author, especially on small ones like this which new

Re: Questionnaire

On Thursday, 9 February 2017 at 10:38:11 UTC, Johannes Pfau wrote: But OTOH I'm an electrical engineer as well ;-) Haha! Then this (https://www.youtube.com/watch?v=D7Sd8A6_fYU=youtu.be=2389) is for you ;-) "What we know is that C code will compile all sorts of bugs, more so than most

Re: Questionnaire

Am Wed, 08 Feb 2017 21:41:24 + schrieb Mike : > On Wednesday, 8 February 2017 at 18:27:57 UTC, Ilya Yaroshenko > wrote: > > 1. Why your company uses D? > > We don't use D. > > > 2. Does your company uses C/C++, Java, Scala, Go, Rust? > > C/C++. Currently exploring

Re: Questionnaire

1. Why your company uses D? I can use D only for very small apps in my job. My own project use D because it was the best language what I found when I started developing OS from scratch 5 years ago. 2. Does your company uses C/C++, Java, Scala, Go, Rust? We use C/C++, Java 3. If yes,

Re: two points

On 2/8/2017 11:09 PM, Nick Sabalausky wrote: And any PRs I have managed to get through were all uphill battles the whole way. You have contributed 5 PRs to dmd: https://github.com/dlang/dmd/pulls?q=is%3Apr+author%3Aabscissa 1 is open (it's controversial) 1 closed (today by me)

Re: two points

On Thursday, 9 February 2017 at 08:02:23 UTC, Walter Bright wrote: I do not understand using pseudonyms on github. It can hardly be a privacy issue, as github doesn't hide your name. But it definitely impedes your "brand", i.e. your reputation, as it becomes divided in two. Github does not

Re: Questionnaire

On Wednesday, 8 February 2017 at 21:41:24 UTC, Mike wrote: * "Minimal Runtime" is the building block of systems programming. If this is not a core feature of a language, it will never compete with C. Systems programmers in my field need to incrementally opt-in to features in a pay-as-you-go

Re: two points

On 2/8/2017 11:09 PM, Nick Sabalausky wrote: I fixed an issue where "///"-style doc comments resulted in excessive paragraph breaks...must've been over a year ago. Simple fix for a nagging bug. The fix worked. Caused no problems. No controversy. And to this day, just went completely ignored