Re: DIP 1030--Named Arguments--Final Review Begins
On Tuesday, 28 July 2020 at 05:14:46 UTC, Mike Parker wrote: On Tuesday, 28 July 2020 at 04:18:11 UTC, Cecil Ward wrote: Mike, is this going to go ahead? You can see the status of every active DIP here: https://github.com/dlang/DIPs/blob/master/DIPs/README.md As a rule, every DIP in that top table is going to go ahead unless a) the author explicitly asks me to stop or postpone the process or b) the author becomes unresponsive. You'll see there that 1030 is currently in Formal Assessment, meaning Walter and Atila are evaluating it. I emailed them a few days ago to kick it off, so we should hear a verdict in the next two or three weeks. And thanks for asking! You've made me realize I should start announcing when a Formal Assessment begins. Thanks Mike, I’m very new to this game. Best, Cecil Ward.
Re: DIP 1030--Named Arguments--Final Review Begins
On Tuesday, 28 July 2020 at 04:18:11 UTC, Cecil Ward wrote: Mike, is this going to go ahead? You can see the status of every active DIP here: https://github.com/dlang/DIPs/blob/master/DIPs/README.md As a rule, every DIP in that top table is going to go ahead unless a) the author explicitly asks me to stop or postpone the process or b) the author becomes unresponsive. You'll see there that 1030 is currently in Formal Assessment, meaning Walter and Atila are evaluating it. I emailed them a few days ago to kick it off, so we should hear a verdict in the next two or three weeks. And thanks for asking! You've made me realize I should start announcing when a Formal Assessment begins.
Re: DIP 1030--Named Arguments--Final Review Begins
On Monday, 11 May 2020 at 11:49:22 UTC, Mike Parker wrote: The Final Review for DIP 1030, "Named Arguments", has begun. The purpose of the Final Review is a last check to make sure everything is in good shape. Generally, we aren't looking for major revisions to the DIP unless someone notices something critical. This is a chance for any revisions made in the previous review round to be scrutinized. Even if no revisions were made, it's a final opportunity to catch any problems that may have been missed before. [...] Mike, is this going to go ahead?
Re: tsv-utils 2.0 release: Named field support
On Monday, 27 July 2020 at 14:32:27 UTC, aberba wrote: On Sunday, 26 July 2020 at 20:28:56 UTC, Jon Degenhardt wrote: I'm happy to announce a new major release of eBay's TSV Utilities. The 2.0 release supports named field selection in all of the tools, a significant usability enhancement. So I didn't checked it out until today and I'm really impressed about the documentation, presentation and just about everything. Thanks for the kind words, and for taking the time to check out the toolkit. Both are very much appreciated!
Re: tsv-utils 2.0 release: Named field support
On 7/27/20 7:32 AM, aberba wrote: > Goes to show most of us will do just fine with GC code. Our job is to > learn how to use it well. Exactly. My programs sometimes run for minutes on dozens of gigabytes of files. Compared to that, the number of and the total time spent for garbage collections is comically low.[1] Ali [1] Michael Parker shows how to profile the GC here: https://dlang.org/blog/2017/06/16/life-in-the-fast-lane/ Spoiler: It's as simple as passing the --DRT-gcopt=profile:1 command line option to any compiled program.
Re: tsv-utils 2.0 release: Named field support
On Sunday, 26 July 2020 at 20:28:56 UTC, Jon Degenhardt wrote: Hi all, I'm happy to announce a new major release of eBay's TSV Utilities. The 2.0 release supports named field selection in all of the tools, a significant usability enhancement. [...] So I didn't checked it out until today and I'm really impressed about the documentation, presentation and just about everything. I personally don't do data science and related stuff, yet. However I'm sure my data science friend is REALLY going to like this. Unnecessary GC allocation was avoided, but GC was used rather than manual memory management. Higher-level I/O primitives were used rather than custom buffer management. Goes to show most of us will do just fine with GC code. Our job is to learn how to use it well.
