Re: Release D 2.073.0
On 1/27/2017 4:43 PM, deadalnix wrote: I mostly went silent on this because I this point, I have no idea how to reach to you and Andrei. This is bad because of all the same reasons inout is bad, plus some other on its own, and is going down exactly like inout so far, plus some extra problems on its own. If you've got a case, make it. If you see problems, explain. If you want to help, please do.
Re: Release D 2.073.0
On Friday, 27 January 2017 at 19:12:37 UTC, Walter Bright wrote: Yes, I'm 100% responsible for 'return scope' and pushing it harder than most people probably would like. Maybe I'm alone, but I strongly believe it is critical to D's future. You sound like this guy: http://www.drdobbs.com/cpp/type-qualifiers-and-wild-cards/231902461
Re: Release D 2.073.0
On Friday, 27 January 2017 at 19:09:30 UTC, Walter Bright wrote: On 1/26/2017 5:42 AM, Dicebot wrote: https://issues.dlang.org/show_bug.cgi?id=17123 Can I have my "I told you so" badge please? Yes, you may. But nobody promised there would be no regressions - just that we'll fix them. I'll see about taking care of this one. Thanks for reporting it. Regressions are the symptoms. I mostly went silent on this because I this point, I have no idea how to reach to you and Andrei. This is bad because of all the same reasons inout is bad, plus some other on its own, and is going down exactly like inout so far, plus some extra problems on its own.
Re: Silicon Valley D Meetup - January 26, 2017 - "High Performance Tools in D" by Jon Degenhardt
On Friday, 27 January 2017 at 20:48:30 UTC, Ali Çehreli wrote: On 01/27/2017 08:21 AM, Jack Stouffer wrote: On Friday, 27 January 2017 at 03:58:26 UTC, Ali Çehreli wrote: And this: http://youtu.be/-DK4r5xewTY Hey Jon, if you're in this thread, are you able to post any of the code that you use for tsv parsing? Yeah, the slide starting at 19'35 is the most interesting: https://www.youtube.com/watch?v=-DK4r5xewTY&feature=youtu.be&t=1175 Tools written in D (mostly with Phobos and with GC) are at least 3 times faster! Let's verify the results and then make some noise. :) Ali An independent verification of the results would be fantastic. Any time a single person does this type of benchmark, especially the author of the tool, there's real risk of an error. In this case I took every reasonable step I knew to be diligent about it, but still. And yes, the deltas are impressive. I was surprised.
Re: Silicon Valley D Meetup - January 26, 2017 - "High Performance Tools in D" by Jon Degenhardt
On 01/27/2017 08:21 AM, Jack Stouffer wrote: On Friday, 27 January 2017 at 03:58:26 UTC, Ali Çehreli wrote: And this: http://youtu.be/-DK4r5xewTY Hey Jon, if you're in this thread, are you able to post any of the code that you use for tsv parsing? Yeah, the slide starting at 19'35 is the most interesting: https://www.youtube.com/watch?v=-DK4r5xewTY&feature=youtu.be&t=1175 Tools written in D (mostly with Phobos and with GC) are at least 3 times faster! Let's verify the results and then make some noise. :) Ali
Re: Release D 2.073.0
On 1/27/2017 3:12 AM, Dicebot wrote: And also stuff like https://github.com/dlang/druntime/pull/1740 I'm curious what is wrong with that? I think the story behind `return scope` is the critical point for me. It is worst technical disaster that has happened to compiler in years, and I am going to blame Walter personally for it. Yes, I'm 100% responsible for 'return scope' and pushing it harder than most people probably would like. Maybe I'm alone, but I strongly believe it is critical to D's future.
Re: Release D 2.073.0
On 1/26/2017 5:42 AM, Dicebot wrote: https://issues.dlang.org/show_bug.cgi?id=17123 Can I have my "I told you so" badge please? Yes, you may. But nobody promised there would be no regressions - just that we'll fix them. I'll see about taking care of this one. Thanks for reporting it.
Re: Silicon Valley D Meetup - January 26, 2017 - "High Performance Tools in D" by Jon Degenhardt
On Friday, 27 January 2017 at 16:21:51 UTC, Jack Stouffer wrote: On Friday, 27 January 2017 at 03:58:26 UTC, Ali Çehreli wrote: And this: http://youtu.be/-DK4r5xewTY Hey Jon, if you're in this thread, are you able to post any of the code that you use for tsv parsing? Code has been open-sourced: https://github.com/eBay/tsv-utils-dlang The performance benchmarks showed in the talk are not in the repo, the benchmarks currently listed are from a year ago. I'm planning to update the repo in the next few weeks, probably after the next LDC release. If there are questions about specific types of things perhaps a thread in General forum would work. --Jon
Re: Silicon Valley D Meetup - January 26, 2017 - "High Performance Tools in D" by Jon Degenhardt
On Friday, 27 January 2017 at 03:58:26 UTC, Ali Çehreli wrote: And this: http://youtu.be/-DK4r5xewTY Hey Jon, if you're in this thread, are you able to post any of the code that you use for tsv parsing?
Re: Release D 2.073.0
On 01/27/2017 01:29 PM, Nordlöw wrote: > On Friday, 27 January 2017 at 11:12:22 UTC, Dicebot wrote: >> And also stuff like https://github.com/dlang/druntime/pull/1740 - I >> think the story behind `return scope` is the critical point for me. It >> is worst technical disaster that has happened to compiler in years, >> and I am going to blame Walter personally for it. > > So what would the alternative be? Alternative would be to implement new functionality like a responsible developer - keep it in sync with specification document, design set of acceptance tests and do all the development in a separate branch until is verified to both have desired semantics and don't cause any breakage in existing projects. And don't rush into forcing usage of half-done feature inside standard library the very moment it got released. signature.asc Description: OpenPGP digital signature
Re: Release D 2.073.0
On Friday, 27 January 2017 at 11:12:22 UTC, Dicebot wrote: And also stuff like https://github.com/dlang/druntime/pull/1740 - I think the story behind `return scope` is the critical point for me. It is worst technical disaster that has happened to compiler in years, and I am going to blame Walter personally for it. So what would the alternative be?
Re: Release D 2.073.0
On Friday, 27 January 2017 at 11:12:22 UTC, Dicebot wrote: And also stuff like https://github.com/dlang/druntime/pull/1740 Why it would break code if `in` meant `scope`?
Re: Release D 2.073.0
And also stuff like https://github.com/dlang/druntime/pull/1740 - I think the story behind `return scope` is the critical point for me. It is worst technical disaster that has happened to compiler in years, and I am going to blame Walter personally for it.
