Re: DIP: Tail call optimization

2016-07-09 Thread Jack Stouffer via Digitalmars-d-announce
On Sunday, 10 July 2016 at 06:29:43 UTC, A.B wrote: Get fucked by yourself asshole ! Your penance is that you'll have to review all the crappy DIPs that will come on GH until your death, now that anyone can post his fantastic idea easily. Hahahahaha. Go back to >>>/g/

Re: DIP: Tail call optimization

2016-07-09 Thread Dietrich Daroch via Digitalmars-d-announce
On Sunday, 10 July 2016 at 06:17:08 UTC, ketmar wrote: On Sunday, 10 July 2016 at 05:55:50 UTC, Dietrich Daroch wrote: Yes, it probably does TCO. The problem is what if you think it does and it cannot do it because of a misunderstanding on when it can be applied or a bug? there can't be any "

Re: DIP: Tail call optimization

2016-07-09 Thread Dietrich Daroch via Digitalmars-d-announce
On Sunday, 10 July 2016 at 06:18:41 UTC, Jack Stouffer wrote: On Sunday, 10 July 2016 at 05:55:50 UTC, Dietrich Daroch wrote: Yes, it probably does TCO. The problem is what if you think it does and it cannot do it because of a misunderstanding on when it can be applied or a bug? Then file a b

Re: DIP: Tail call optimization

2016-07-09 Thread ketmar via Digitalmars-d-announce
On Sunday, 10 July 2016 at 06:37:18 UTC, ketmar wrote: On Sunday, 10 July 2016 at 06:20:59 UTC, Seb wrote: ... guys, please stay friendly, constructive and polite! I thought we are all grown-ups here! i do. someone who is not able to understand when and how TCO works is clearly brain-damaged.

Re: DIP: Tail call optimization

2016-07-09 Thread ketmar via Digitalmars-d-announce
On Sunday, 10 July 2016 at 06:20:59 UTC, Seb wrote: ... guys, please stay friendly, constructive and polite! I thought we are all grown-ups here! i do. someone who is not able to understand when and how TCO works is clearly brain-damaged. if he isn't, why did he become programmer in the first

Re: DIP: Tail call optimization

2016-07-09 Thread A.B via Digitalmars-d-announce
On Sunday, 10 July 2016 at 06:20:59 UTC, Seb wrote: On Sunday, 10 July 2016 at 06:17:17 UTC, A.B wrote: On Sunday, 10 July 2016 at 05:55:50 UTC, Dietrich Daroch wrote: On Sunday, 10 July 2016 at 05:24:49 UTC, A.B wrote: On Sunday, 10 July 2016 at 05:03:46 UTC, Dietrich Daroch wrote: [...] T

Re: DIP: Tail call optimization

2016-07-09 Thread Seb via Digitalmars-d-announce
On Sunday, 10 July 2016 at 06:17:17 UTC, A.B wrote: On Sunday, 10 July 2016 at 05:55:50 UTC, Dietrich Daroch wrote: On Sunday, 10 July 2016 at 05:24:49 UTC, A.B wrote: On Sunday, 10 July 2016 at 05:03:46 UTC, Dietrich Daroch wrote: [...] That's crap...I disassemble DMD output some time to ti

Re: DIP: Tail call optimization

2016-07-09 Thread Jack Stouffer via Digitalmars-d-announce
On Sunday, 10 July 2016 at 05:55:50 UTC, Dietrich Daroch wrote: Yes, it probably does TCO. The problem is what if you think it does and it cannot do it because of a misunderstanding on when it can be applied or a bug? Then file a bug report?

Re: DIP: Tail call optimization

2016-07-09 Thread A.B via Digitalmars-d-announce
On Sunday, 10 July 2016 at 05:55:50 UTC, Dietrich Daroch wrote: On Sunday, 10 July 2016 at 05:24:49 UTC, A.B wrote: On Sunday, 10 July 2016 at 05:03:46 UTC, Dietrich Daroch wrote: Hi everyone (= I've just added a new proposal to add a new attribute to ensure TCO is applied. The proposal is

Re: DIP: Tail call optimization

2016-07-09 Thread ketmar via Digitalmars-d-announce
On Sunday, 10 July 2016 at 05:55:50 UTC, Dietrich Daroch wrote: Yes, it probably does TCO. The problem is what if you think it does and it cannot do it because of a misunderstanding on when it can be applied or a bug? there can't be any "misunderstanding" from compiler side. either it is a le

Re: DIP: Tail call optimization

2016-07-09 Thread Dietrich Daroch via Digitalmars-d-announce
On Sunday, 10 July 2016 at 05:24:49 UTC, A.B wrote: On Sunday, 10 July 2016 at 05:03:46 UTC, Dietrich Daroch wrote: Hi everyone (= I've just added a new proposal to add a new attribute to ensure TCO is applied. The proposal is really simple, but I'm clueless on how to implement it and also

Re: DIP: Tail call optimization

2016-07-09 Thread A.B via Digitalmars-d-announce
On Sunday, 10 July 2016 at 05:03:46 UTC, Dietrich Daroch wrote: Hi everyone (= I've just added a new proposal to add a new attribute to ensure TCO is applied. The proposal is really simple, but I'm clueless on how to implement it and also interested on getting feedback on it. The proposal

DIP: Tail call optimization

2016-07-09 Thread Dietrich Daroch via Digitalmars-d-announce
Hi everyone (= I've just added a new proposal to add a new attribute to ensure TCO is applied. The proposal is really simple, but I'm clueless on how to implement it and also interested on getting feedback on it. The proposal it's ready for merge on the new [DIPs repo](https://github.com/

Re: Vision document for H2 2016

2016-07-09 Thread Chris Wright via Digitalmars-d-announce
On Sat, 09 Jul 2016 19:17:31 +, Eugene wrote: > On Thursday, 7 July 2016 at 19:55:51 UTC, Andrei Alexandrescu wrote: >> https://wiki.dlang.org/Vision/2016H2 -- Andrei > > is it possible to make a modular D language(and a compiler), so one just > could release new features of the language with

Re: Announcing new DIP handling process

2016-07-09 Thread ZombineDev via Digitalmars-d-announce
On Saturday, 9 July 2016 at 21:21:54 UTC, Dicebot wrote: On 07/09/2016 09:11 PM, ZombineDev wrote: Can the new DIP process be used to evaluate library proposals? That way a high level design could be fleshed out and approved before the contributor goes too far with implementing a design which

Re: Announcing new DIP handling process

2016-07-09 Thread Dicebot via Digitalmars-d-announce
On 07/09/2016 09:11 PM, ZombineDev wrote: > Can the new DIP process be used to evaluate library proposals? That way > a high level design could be fleshed out and approved before the > contributor goes too far with implementing a design which would be > rejected. It is quite hard. To reasonably ev

Re: Battle-plan for CTFE

2016-07-09 Thread Stefan Koch via Digitalmars-d-announce
On Monday, 9 May 2016 at 16:57:39 UTC, Stefan Koch wrote: Hi Guys, I have been looking into the DMD now to see what I can do about CTFE. [ ] I will post more details as soon as I dive deeper into the code. I decided to keep a gist updated to represent the current state the new engine c

Re: Vision document for H2 2016

2016-07-09 Thread Eugene via Digitalmars-d-announce
On Thursday, 7 July 2016 at 19:55:51 UTC, Andrei Alexandrescu wrote: https://wiki.dlang.org/Vision/2016H2 -- Andrei is it possible to make a modular D language(and a compiler), so one just could release new features of the language without releasing a new version of a compiler(ldc, etc.), and

Re: Announcing new DIP handling process

2016-07-09 Thread ZombineDev via Digitalmars-d-announce
On Saturday, 9 July 2016 at 12:56:48 UTC, Dicebot wrote: After quite some preliminary discussions and preparations, new D Improvement Proposals handling process is finally happenning. Please read description and explanation here: https://github.com/dlang/DIPs ## Rationale There are two main

Re: Vision document for H2 2016

2016-07-09 Thread Robert M. Münch via Digitalmars-d-announce
On 2016-07-08 20:46:21 +, Walter Bright said: On 7/8/2016 6:51 AM, Robert M. Münch wrote: 1. Fixing (all) bugs before doing new things: If I look as a CTO, CIO or CEO on ... I have yet to find any engineering product in any field that doesn't have open issues. A more practical question i

Re: Vision document for H2 2016

2016-07-09 Thread Robert M. Münch via Digitalmars-d-announce
On 2016-07-08 18:07:39 +, Andrei Alexandrescu said: On 07/08/2016 09:51 AM, Robert M. Münch wrote: 1. Fixing (all) bugs before doing new things: If I look as a CTO, CIO or CEO on D I the first thing I ask is: "Are they doing a lot of new stuff? And if, is this thing / last releasae that bul

Re: NanoSVG port

2016-07-09 Thread ketmar via Digitalmars-d-announce
just make sure to download the latest version by the given link before you want to try it. ;-) glad to see that you found it useful

Re: Announcing new DIP handling process

2016-07-09 Thread Andrei Alexandrescu via Digitalmars-d-announce
On 07/09/2016 09:11 AM, Seb wrote: On Saturday, 9 July 2016 at 12:56:48 UTC, Dicebot wrote: After quite some preliminary discussions and preparations, new D Improvement Proposals handling process is finally happenning. Please read description and explanation here: [...] Sweet! A bit of noise:

Re: Announcing new DIP handling process

2016-07-09 Thread Seb via Digitalmars-d-announce
On Saturday, 9 July 2016 at 12:56:48 UTC, Dicebot wrote: After quite some preliminary discussions and preparations, new D Improvement Proposals handling process is finally happenning. Please read description and explanation here: [...] Sweet! A bit of noise: https://www.reddit.com/r/program

Re: NanoSVG port

2016-07-09 Thread Dmitry via Digitalmars-d-announce
On Saturday, 9 July 2016 at 11:06:34 UTC, ketmar wrote: i also made NanoSVG[1] port[2]: simple SVG parser and rasterizer. it is using `malloc()` to allocate memory, but otherwise was rewritten to use `const(char)[]` input for svg, and do not use `sscanf()` from libc. the port lives in NanoVG

Announcing new DIP handling process

2016-07-09 Thread Dicebot via Digitalmars-d-announce
After quite some preliminary discussions and preparations, new D Improvement Proposals handling process is finally happenning. Please read description and explanation here: https://github.com/dlang/DIPs ## Rationale There are two main goals for going this way: 1) Ensure communication between la

NanoSVG port

2016-07-09 Thread ketmar via Digitalmars-d-announce
i also made NanoSVG[1] port[2]: simple SVG parser and rasterizer. it is using `malloc()` to allocate memory, but otherwise was rewritten to use `const(char)[]` input for svg, and do not use `sscanf()` from libc. the port lives in NanoVG package, but it is actually completely independent. [