Re: Battle-plan for CTFE
On Saturday, 9 July 2016 at 20:09:14 UTC, Stefan Koch wrote: I decided to keep a gist updated to represent the current state the new engine can handle. https://gist.github.com/UplinkCoder/89faa06311e417aa93ea99bc92934d3e This is the currentState after approx. 50 hours of work First StringIndexing works now. The next step is getting structs right,
Re: First dmd nightly shipping with dub
On Thursday, 7 July 2016 at 03:26:57 UTC, Suliman wrote:
On Wednesday, 6 July 2016 at 14:53:56 UTC, Jack Stouffer wrote:
On Wednesday, 6 July 2016 at 09:28:44 UTC, Martin Nowak wrote:
This is the first nightly dmd build that includes dub
binaries.
http://nightlies.dlang.org/dmd-2016-07-06/
They will also be part of the upcoming 2.072.y releases.
We will sync the dub and dmd release cycles, but not the
versioning.
Good :)
dfmt and dscanner coming as well?
+1
@{Suliman, JackStouffer}: probably the best way to track and
influence this are these two issues:
https://github.com/Hackerpilot/Dscanner/issues/353
https://github.com/Hackerpilot/dfmt/issues/249
Re: DIP1001: Exception Handling Extensions
On Sunday, 10 July 2016 at 19:55:37 UTC, Superstar64 wrote: link: https://github.com/dlang/DIPs/pull/9 file: https://github.com/Superstar64/DIPs/blob/exception_extensions/DIPs/DIP1001.md I extended this DIP to add @throws(auto) and inference for auto and template functions.
From the Blog: The DLang Vision and Improvement Process
Unlike previous posts on the D Blog, I prepared this one in advance and thought I had it set to auto publish at 9:00 pm my time. So I was surprised to discover at 7:00 pm local time that the post had gone live an hour before (at 9:00 am GMT). I had completely forgotten that, unlike my personal blogs, I had chosen to configure the blog software to use GMT rather than KST. Oh, well. It's live. I'm going to hold off another hour or two before posting it to reddit. I'll share the link here once I have. [1] http://dlang.org/blog/2016/07/13/the-dlang-vision-and-improvement-process/
Re: Announcing new DIP handling process
I have added new "tips" section to the process readme (https://github.com/dlang/DIPs#advices-for-writing-great-dips) to make potential DIP authors less excited and more prepared to real work awaiting ahead :)
Re: From the Blog: The DLang Vision and Improvement Process
On Wednesday, 13 July 2016 at 10:23:44 UTC, Mike Parker wrote: Oh, well. It's live. I'm going to hold off another hour or two before posting it to reddit. I'll share the link here once I have. https://www.reddit.com/r/programming/comments/4smqd2/from_the_d_blog_the_dlang_vision_and_improvement/
Re: From the Blog: The DLang Vision and Improvement Process
On Wednesday, 13 July 2016 at 10:23:44 UTC, Mike Parker wrote: Unlike previous posts on the D Blog, I prepared this one in advance and thought I had it set to auto publish at 9:00 pm my time. So I was surprised to discover at 7:00 pm local time that the post had gone live an hour before (at 9:00 am GMT). I had completely forgotten that, unlike my personal blogs, I had chosen to configure the blog software to use GMT rather than KST. Oh, well. It's live. I'm going to hold off another hour or two before posting it to reddit. I'll share the link here once I have. [1] http://dlang.org/blog/2016/07/13/the-dlang-vision-and-improvement-process/ Well written, keep up the good work!
Re: From the Blog: The DLang Vision and Improvement Process
On 2016-07-13 12:23, Mike Parker wrote: Unlike previous posts on the D Blog, I prepared this one in advance and thought I had it set to auto publish at 9:00 pm my time. So I was surprised to discover at 7:00 pm local time that the post had gone live an hour before (at 9:00 am GMT). I had completely forgotten that, unlike my personal blogs, I had chosen to configure the blog software to use GMT rather than KST. Oh, well. It's live. I'm going to hold off another hour or two before posting it to reddit. I'll share the link here once I have. BTW, the reader view in Safari works now. Not sure if you did anything special. -- /Jacob Carlborg
Re: DIP: Tail call optimization
On Tuesday, 12 July 2016 at 10:46:01 UTC, Dmitry Olshansky 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. [...] In contrast to what many folks expect, TCO is affecting program semantics in a way that changes stack overflow to normal execution. Therefore it's not an optimization but part of semantics, and there should be a way to mark a call as a tail-call in any optimization level. Yes, it's not a tiny detail that improves performance a bit, but it decides wheter the built binary works or not. Also, some people are against breakage, but having a correctly built binary that may surprise you with a stack overflow when ported is not something I would call real portability.
