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
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
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
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
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
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
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.),
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
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
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
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
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
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:
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
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
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.
p.s. it is, btw, completely possible to add at least something
like "ctfe tracer" (something like old basic "trace on" command),
or even some kind of gdb-like debugger to ctfe engine.
it won't, of course, find it's way into mainline, but may still
be a fun project to do.
On Friday, 8 July 2016 at 23:31:38 UTC, Stefan Koch wrote:
and mine is segfaulting in some bizarre ways (i failed my basic
++ and -- math, and so the stack ;-).
still, it is almost working, with support for both compiled and
interpreted function calls, almost full range of integer math and
18 matches
Mail list logo
