Re: The 10k Twitter Target
On Monday, 16 April 2018 at 08:39:05 UTC, Mike Parker wrote: If you have a Twitter handle, it would help us out to retweet anything interesting you see on @D_Programming. The link in the navbar should probably link to this twitter handle rather than the hash tag.
Re: DConf 2018 Hackathon -- now open to the public free of charge
On Tuesday, 27 March 2018 at 14:04:29 UTC, Mike Parker wrote: Yesterday, I made the announcement that the Hackathon would be open to anyone willing to pay $100 to get in. That idea has now been nixed. Instead, anyone can come in for the full day completely free. It's like a big Munich Meetup! Wow, it's great news that the D Foundation can afford to do that ;)
Re: Release D 2.079.0
On Tuesday, 6 March 2018 at 12:21:41 UTC, Steven Schveighoffer wrote: That being said, I'm wondering if it wouldn't be better to have std.experimental be in its own repository. This allows selection of the dependency on std.experimental separate from phobos. It still would be an "official" dlang package, and might even be included in the distribution (the latest version anyway), and docs included on the website. But if needed, you could have your dub package depend on a prior version. The entire concept needs a reexamination IMO. I just checked the git history, and not one module has graduated from std.experimental to mainline Phobos since the idea's inception in 2014. While it's possible that none of the modules are ready, logger has been there for four years now. I was against changing how experimental is handled in the past, but I recently have started to rethink how we promote modules. Also, if you'll allow me to have crazy ideas for a moment, one wonders why we shouldn't just release Phobos itself through dub? Rust makes people use their build tool, why not us?
Re: Proposal for a standard Decimal type in alpha
On Thursday, 21 December 2017 at 13:59:28 UTC, Jack Stouffer wrote: ... While I believe my library has certain API advantages, I'm really not interested in duplicating a bunch of work when rumbu's version is pretty much complete, so I'm dropping this.
Re: Proposal for a standard Decimal type in alpha
On Friday, 5 January 2018 at 15:44:57 UTC, H. S. Teoh wrote: On Fri, Jan 05, 2018 at 03:38:45PM +, Jack Stouffer via Digitalmars-d-announce wrote: On Friday, 5 January 2018 at 15:22:01 UTC, H. S. Teoh wrote: > Very nice to see this taking shape. What's the link to the > code again? https://github.com/JackStouffer/stdxdecimal Thanks! Will take a look sometime. Might throw in a PR or two if I can. T Well hold off on that for a day because I just realized I have to redesign the internals of the whole thing due to a bug I found. Long story short, I'd been using a myriad of different types (depending on your chosen precision) to represent the coefficient in order to avoid the slowness of BigInt. But I realized due to a bug that this isn't really a workable solution. I'm going to change the code to always use a BigInt, and just work on making BigInt faster where I can. This will make the Decimal code about half as complex thankfully.
Re: Proposal for a standard Decimal type in alpha
On Friday, 5 January 2018 at 15:22:01 UTC, H. S. Teoh wrote: Very nice to see this taking shape. What's the link to the code again? https://github.com/JackStouffer/stdxdecimal
Re: Proposal for a standard Decimal type in alpha
On Thursday, 21 December 2017 at 13:59:28 UTC, Jack Stouffer wrote: ... Updated version out: * Added unary +,-,++,-- * Added casting to bool and floating point types * Added static ctors for infinite and nan for floating point type compatibility * Added abs, isNaN, isInfinite * Added support to opBinary for mixing different precision levels on each side of the operation
Re: Release D 2.078.0
On Thursday, 4 January 2018 at 15:53:33 UTC, Mike Parker wrote: On a related note, the vision document for 2018H1 has not yet been created. It's a WIP. If I may make a suggestion, please make the vision documents smaller and more focused. The goals laid out are typically far too broad to actually accomplish in half a year. Instead, the document should give detailed milestones for two or three long term goals which the community should complete in the six months. E.g. @safety: we aim to enable large-scale uses of D with safety guarantees and Static introspection: We believe this is an important strategic advantage of D and we should continue to improve both compiler support and library support. These are not actionable and can't be achieved in just six months of work. Instead, something like To move toward a @safe Phobos, std.json, std.file, and std.stdio should all be 100% @safe by June. Static introspection: we believe this is an important strategic advantage of D, so X, Y, and Z feature should be added by June gives contributors goals they can start making PRs for.
Re: Beta 2.078.0
On Saturday, 30 December 2017 at 14:34:13 UTC, Martin Nowak wrote: On Tuesday, 19 December 2017 at 22:51:59 UTC, Martin Nowak wrote: First beta for the 2.078.0 release. Release Candidate is tagged and uploaded, website will be updated soon. http://downloads.dlang.org/pre-releases/2.x/2.078.0/ https://github.com/dlang/dlang.org/commit/362da850fa65a20f0b68b76786bb6a57840b6c59 Martin, before you release 2.078, could you please comment on the problem of issuing a warning for issue 16997 https://issues.dlang.org/show_bug.cgi?id=18148
Re: Proposal for a standard Decimal type in alpha
On Thursday, 21 December 2017 at 23:08:22 UTC, Andre Pany wrote: That are fantastic news. Thanks for working on this topic. Is it possible to define a decimal type with a defined scale and precision? From the examples and the documentation I am not sure whether it is possible. Yes, the Hook template parameter currently controls how many significant digits your decimal can have and will eventually be able to control the min and max allowed exponents as well. By default, it's set at 9 digits, but you can have as many as int.max - 1 since it auto uses BigInt under the hood. Once your decimal has more than the allowed number of digits, it's rounded according to the Hook prescribed rounding method, which is half up by default.
Proposal for a standard Decimal type in alpha
A couple of months ago, Andrei noted that a donor asked for a precise decimal type for D specifically: https://forum.dlang.org/post/osnema$d5s$1...@digitalmars.com. I've also heard this asked for many times, so I decided to start work on a library for eventual proposal to Phobos. I just finished getting the type into an alpha version, and I wanted to solicit people's opinions on the API and if I'm heading in the right direction with this. The dub page: https://code.dlang.org/packages/stdxdecimal The docs: https://jackstouffer.github.io/stdxdecimal/ What you can do so far: * Control behavior with a Hook type a-la std.experimental.checkedint * Addition, subtraction, multiplication, division * Construction from a strings and built-in number types For the full list of planned features, see: https://github.com/JackStouffer/stdxdecimal Please let me know what you think!
Re: static foreach is now in github master
On Tuesday, 18 July 2017 at 15:46:04 UTC, Seb wrote: https://is.gd/1TCQOh Hmmm, that code is printing 0 1 2 3 0 1 2 3 for me. Shouldn't it just be printing once?
Re: docarchives.dlang.io - go back in time to previous released versions of dlang.org
On Tuesday, 4 July 2017 at 01:39:23 UTC, Seb wrote: ... Thanks for doing this. IMO there should be a link under the "switch to pre-release." link in the current docs. Maybe replace it with a dropdown to select the version from 2.066 to pre-release?
Re: DIP 1003 (Remove body as a Keyword) Accepted!
On Saturday, 3 June 2017 at 06:09:21 UTC, Jonathan M Davis wrote: On Saturday, June 03, 2017 02:00:13 Jack Stouffer via Digitalmars-d-announce wrote: I recommend a longer deprecation cycle than usual for this, as this will break many legacy libraries that don't get maintained often. A period of two years sounds about right. For Phobos, that _is_ the normal length of the deprecation cycle. For the language itself, I don't think that it's anywhere near as consistent, but I've gotten the impression that deprecations in the language usually stick around for quite awhile, but I haven't exactly tracked it closely, so I don't know. - Jonathan M Davis All of the recent Phobos deprecations have been a year. 18 months at most.
Re: DIP 1003 (Remove body as a Keyword) Accepted!
On Friday, 2 June 2017 at 14:17:10 UTC, Mike Parker wrote: Congratulations, Jared! https://github.com/dlang/DIPs/blob/master/DIPs/DIP1003.md Congratulations. I recommend a longer deprecation cycle than usual for this, as this will break many legacy libraries that don't get maintained often. A period of two years sounds about right.
Re: DCompute is now in the master branch of LDC
On Tuesday, 30 May 2017 at 18:06:56 UTC, Walter Bright wrote: I fear the conversation will go like this, like it has for me: N: DCompute W: What's DCompute? N: Enables GPU programming with D W: Cool! instead of: N: D-GPU W: Cool! I can use D to program GPUs! This was literally what happened to me when I saw the headline.
Re: Faster Command Line Tools in D
On Wednesday, 24 May 2017 at 21:46:10 UTC, cym13 wrote: I am disappointed because there are so many good things to say about this, so many good questions or remarks to make when not familiar with the language, and yet all we get is "Meh, this benchmark shows nothing of D's speed against Python". Wouldn't be the first time https://news.ycombinator.com/item?id=10828450
Re: DCOnf 2017 videos online
On Sunday, 7 May 2017 at 18:11:47 UTC, Patrick Schluter wrote: It looks like the good people of Sociomantic have already posted videos of the Dconf2017 on youtube. https://www.youtube.com/channel/UC54uUlXuGhigMsdaNtP6THQ Enjoy. Anyone know why the Q section of Walter's talk was muted?
Re: DCOnf 2017 videos online
On Sunday, 7 May 2017 at 21:36:30 UTC, Mike Parker wrote: On Sunday, 7 May 2017 at 18:11:47 UTC, Patrick Schluter wrote: It looks like the good people of Sociomantic have already posted videos of the Dconf2017 on youtube. https://www.youtube.com/channel/UC54uUlXuGhigMsdaNtP6THQ Enjoy. And here's a direct link to the playlist: https://www.youtube.com/playlist?list=PL3jwVPmk_PRxo23yyoc0Ip_cP3-rCm7eB I assume you're handling the reddit post?
Re: GC blessed for C++ (again)
On Tuesday, 11 April 2017 at 16:50:20 UTC, jmh530 wrote: Is there a non-breaking way to do it that would increase the amount of flexibility while keeping the current behavior as a default? For instance, the equivalent of using std.experimental.allocator so that a user could switch between the default being GCAllocator or Mallocator, or something like that... From what I understand, the plan has always been to start to integrate std.experimental.allocator into Phobos when it stabilizes. There are some questions though: 1. How is this going to be done? Do we have the functions in Phobos allocate with theAllocator? Or, do we pass in an allocator type via template parameter? Or, do we pass in an allocator instance via function parameter? Each solution has it's own pros and cons. 2. How do you make it @safe? For the GC allocator, you can make allocation @safe, but not deallocation. So do you special case GCAllocator in Phobos code to not call GCAllocator.deallocate() and just let the GC collect? 3. How will @safe ref-counting play in with this? Andrei has his sights set on putting all strings in their own ref-counted store in order to make them @safe @nogc. Is RC going to be it's own allocator? I've never seen comprehensive plans or ideas about allocator integration. I've heard rumblings about a collections library that supposed to use it, but never seen anything.
Re: GC blessed for C++ (again)
On Tuesday, 11 April 2017 at 07:02:19 UTC, Swoorup Joshi wrote: Breaking, you mean the standard library? or including user codebases? Taking the GC out of language constructs (e.g. ~=, AAs) would be a massive breaking change and would probably break the majority of D code in existence.
Re: GC blessed for C++ (again)
On Monday, 10 April 2017 at 04:17:21 UTC, Swoorup Joshi wrote: On Wednesday, 28 September 2016 at 20:50:28 UTC, Ali Çehreli wrote: https://www.reddit.com/r/programming/comments/54xnbg/herb_sutters_experimental_deferred_and_unordered/ Ali Is it possible to have something similar as in library rather than GC in core language construct? Not without breaking changes.
Re: dmd Backend converted to Boost License
On Friday, 7 April 2017 at 15:14:40 UTC, Walter Bright wrote: https://github.com/dlang/dmd/pull/6680 Yes, this is for real! Symantec has given their permission to relicense it. Thank you, Symantec! Something that just popped into my head: You've said that you've avoided ever looking at other compiler's code to avoid legal trouble. Is that problem gone now?
Re: dmd Backend converted to Boost License
On Friday, 7 April 2017 at 19:37:14 UTC, Jonathan M Davis wrote: From what I've seen, the fact that we use it so heavily in the D community is abnormal AFAIK the reasons it was chosen were 1. It's as close to public domain as you can get in international law 2. It's on all of the "Accepted OSS Licenses" lists that major corps have because of Boost itself being used in those companies. If your license isn't on the list, your project isn't being used.
Re: dmd Backend converted to Boost License
On Friday, 7 April 2017 at 15:14:40 UTC, Walter Bright wrote: https://github.com/dlang/dmd/pull/6680 Yes, this is for real! Symantec has given their permission to relicense it. Thank you, Symantec! Reddit: https://www.reddit.com/r/programming/comments/6419py/the_official_d_compiler_is_now_free_as_in_freedom/
Re: dmd Backend converted to Boost License
On Friday, 7 April 2017 at 15:14:40 UTC, Walter Bright wrote: https://github.com/dlang/dmd/pull/6680 Yes, this is for real! Symantec has given their permission to relicense it. Thank you, Symantec! A great step forward for the language! A huge thank you to everyone who made this happen.
Re: Beta 2.074.0-b1
On Saturday, 1 April 2017 at 11:14:51 UTC, Martin Nowak wrote: On Tuesday, 28 March 2017 at 10:30:48 UTC, H. S. Teoh wrote: Very cool about the new format!() feature. What about extending this to writef(ln)? That has already been done: see Phobos PR #5296. I'll try to cherry-pick over those as well, doesn't make sense to only release one part. Please try to use the milestones to mark PRs that are supposed to go together. https://github.com/dlang/phobos/pull/5317 Could you please also look at https://github.com/dlang/phobos/pull/5310 Thanks
Re: Beta 2.074.0-b1
On Saturday, 25 March 2017 at 21:35:16 UTC, Moritz Maxeiner wrote: On Saturday, 25 March 2017 at 15:56:41 UTC, Jack Stouffer wrote: Yes, it's still not stable so it will be there for the foreseeable future. For example, just three days ago we pulled in a big bug fix that also was a huge breaking change . Could you please provide a link for that? I've glanced over [1] and wasn't able to identify it easily. [1] https://github.com/dlang/phobos/pulls?q=is%3Apr+is%3Aclosed https://github.com/dlang/phobos/pull/5274
Re: Beta 2.074.0-b1
On Saturday, 25 March 2017 at 15:09:02 UTC, Dsby wrote: What about DIP1000, will it be default? No. Still way too many bugs. will std.experimental.allocator also experimental? Yes, it's still not stable so it will be there for the foreseeable future. For example, just three days ago we pulled in a big bug fix that also was a huge breaking change .
Re: Beta 2.074.0-b1
On Saturday, 25 March 2017 at 05:19:32 UTC, rikki cattermole wrote: On 24/03/2017 6:35 PM, Martin Nowak wrote: First beta for the 2.074.0 release. This release comes with plenty of phobos additions and a new std.experimental module. http://dlang.org/download.html#dmd_beta http://dlang.org/changelog/2.074.0.html Please report any bugs at https://issues.dlang.org -Martin That "new" module isn't documented on the changelog. https://dlang.org/changelog/2.074.0.html#std-experimental-checkedint
Re: D event in Bucharest
On Saturday, 18 March 2017 at 15:02:23 UTC, Andrei Alexandrescu wrote: I'll give a talk on D at University "Politehnica" Bucharest on Friday, March 24. Share wide! https://www.facebook.com/events/267258633731095/ Andrei Will the talk be recorded?
Re: DConf 2017 Hotel - book now!
On Thursday, 2 March 2017 at 12:05:32 UTC, Chris wrote: Here's some good advice: https://www.tripadvisor.ie/ShowTopic-g187323-i135-k7931137-Got_ripped_off_by_taxi_driver_at_Berlin_Airport-Berlin.html No Ubers in Berlin?
Re: Updates to the tsv-utils toolkit
On Wednesday, 22 February 2017 at 18:12:50 UTC, Jon Degenhardt wrote: Speed matters when processing large data files, and these tools are fast. I've published new benchmarks comparing the tools to similar tools written in several native compiled programming languages. The tools are the fastest on five of the six benchmarks run, generally by significant margins. It's a good result for the D programming language. Great news! The specialty toolkits have been anonymized in the tables below. The purpose of these benchmarks is to gauge performance of the D tools, not make comparisons between other toolkits. You're no fun ;)
Re: New (page-per-artifact) standard library doc examples are now editable and runnable
On Friday, 17 February 2017 at 05:06:20 UTC, Seb wrote: Short follow-up: this is now live for the released documentation pages. Enjoy! Please make a post on Reddit! I firmly believe that this puts D at the top of programming language docs. We should advertise!
Re: Beta D 2.073.1-b1
On Thursday, 9 February 2017 at 00:31:17 UTC, Martin Nowak wrote: First beta for the 2.073.1 point release. This version resolves a few regressions and bugs in the 2.073.0 release. http://dlang.org/download.html#dmd_beta http://dlang.org/changelog/2.073.1.html Please report any bugs at https://issues.dlang.org -Martin Please consider https://github.com/dlang/phobos/pull/5113 for inclusion into this release.
Re: two points
On Thursday, 9 February 2017 at 16:48:16 UTC, Joseph Rushton Wakeling wrote: which is that after some initial interest and feedback, the PR just got left alone with no decision to accept or reject it, and no indication of why. This is why I only contribute to Phobos to be quite honest. I count ten active reviewers with pull rights on Phobos. The other repos, tools: one dmd: three druntime: three dlang.org: two
Re: two points
On Thursday, 9 February 2017 at 19:36:52 UTC, Walter Bright wrote: Good idea! Please investigate how to get github to generate such emails. In the meantime, the PR guidelines are here: This is already somewhat done with the PR bot we have. The DlangBot notifies reviewers on the DMD repo, but not Phobos for some reason. All it does on Phobos is auto close bugzilla issues when a bug fix PR is pulled into master. I say enable the bot for Phobos. It would be a small task to also have the bot post the PR guidelines. I think Martin is the maintainer of the bot.
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: Silicon Valley D Meetup - January 26, 2017 - "High Performance Tools in D" by Jon Degenhardt
On Thursday, 26 January 2017 at 07:53:22 UTC, Ali Çehreli wrote: I may post a link to Google Hangouts here at the time of the event (7pm Pacific time). Hopefully, the mic will not be muted. (True story! :p) Ali If it's in hangouts, you can use Hangouts On Air to stream it to YouTube. D could always use more content on YouTube, as Rust and Go swamp us on this point.
Re: Testing in the D Standard Library
On Friday, 20 January 2017 at 16:50:22 UTC, Jacob Carlborg wrote: Could you please create a new image out of the DMD Ddoc output using 2.073.0 instead. It has a completely new default Ddoc theme. But 2.073 isn't released yet.
Re: Testing in the D Standard Library
On Friday, 20 January 2017 at 13:35:40 UTC, Mike Parker wrote: Jack Stouffer details how unit testing, code review, and code coverage are handled in the development and maintenance of Phobos. Thanks, Jack! Blog: https://dlang.org/blog/2017/01/20/testing-in-the-d-standard-library/ Reddit: https://www.reddit.com/r/programming/comments/5p3vlq/testing_in_the_d_standard_library/ Thanks for posting this! Also, there is a typo in the list after the first paragraph. There should be an item which says "A style checker".
Re: Beta 2.073.0-b2
On Sunday, 15 January 2017 at 01:03:26 UTC, Martin Nowak wrote: Second beta for the 2.073.0 release. This adds a few more dmd bugfixes over the first beta. https://github.com/dlang/dmd/compare/v2.073.0-b1...v2.073.0-b2 http://dlang.org/download.html#dmd_beta http://dlang.org/changelog/2.073.0.html Please report any bugs at https://issues.dlang.org -Martin Please be sure to include https://github.com/dlang/druntime/pull/1735 in the next beta.
Re: D Blog Stats
On Friday, 6 January 2017 at 14:54:45 UTC, Mike Parker wrote: I've always enjoyed reading end-of-the year stats at other blogs. I thought it would be fun to do the same for the D Blog. If you've been curious about which posts visitors are viewing, or which links they're clicking, this post is for you. https://dlang.org/blog/2016/06/03/recent-d-foundation-activities/ Don't forget that the majority of programmers use ad and tracking blockers, so I would multiply the view count by at least two to get a more accurate number.
Re: Release D 2.072.0
On Monday, 31 October 2016 at 01:27:08 UTC, Martin Nowak wrote: Glad to announce D 2.072.0. http://dlang.org/download.html This is the release ships with the latest version of dub (v1.1.0), comes with lots of phobos additions and native TLS on OSX. See the changelog for more details. http://dlang.org/changelog/2.072.0.html -Martin https://www.reddit.com/r/programming/comments/5aru4f/d_version_2072_released_over_200_bugs_fixed/
Re: Release 2.071.2
On Monday, 19 September 2016 at 11:08:33 UTC, Martin Nowak wrote: Glad to announce D 2.071.2. http://dlang.org/download.html This point release fixes many issues with the new lookup and import rules. It should be used as a stopgap version when updating older code. The deprecations, the old access checks, and the -transition=import/checkimports switches are planned to be removed with 2.073.x. Those new rules should now be finalized and semantic changes, deprecations, as well as the -transition=import and -transition=checkimports switches should work as expected. Please file a bug if you have any problems. Also see the changelog for more details. http://dlang.org/changelog/2.071.2.html -Martin Thanks for releasing this. On a slightly related note, I think it would be a good idea to branch off 2.072 and start beta testing right away, as it's been five months since the last point release, and A LOT has changed since then. I fear that we may see a huge number of regressions for this beta cycle because they've just been compounding over this time.
Re: yet another event loop
On Wednesday, 24 August 2016 at 18:03:39 UTC, Eugene Wissner wrote: https://github.com/caraus-ecms/tanya Please make documentation easily available for your library. I wish to use event loops in D, but I have no desire to wade though someone else's code in order to figure out how use the library.
Re: Autotesting dub packages with dmd nightly
On Saturday, 16 July 2016 at 20:34:49 UTC, Sebastiaan Koppe wrote: Just to let you guys know - and to be sure no one is doing the same - I decided to go ahead and *start* writing an autotester that will fetch dmd nightly and unittest each dub package. It will be using a classic master-worker architecture and will leverage docker containers. I am aiming really low at first, but will eventually add things like memory usage, history, notifications, etc. Perhaps this code could also be used to find dub packages which are not currently compiling and mark them on code.dlang.org? Which is a feature which people have been asking for for a while.
Re: new cpuid is ready for comments
On Monday, 11 July 2016 at 16:30:44 UTC, Ilya Yaroshenko wrote: Please report your CPU (GitHub/Gist): Late 2015 MacBook Pro Intel i5 https://gist.github.com/JackStouffer/6870bde82788ae039afe0aaf0d7bf4ba
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 Adding another attribute to the language and having the compiler do magic behind the scenes? No thanks.
Re: DIP: Tail call optimization
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
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: Vision document for H2 2016
On Friday, 8 July 2016 at 16:55:54 UTC, Andrei Alexandrescu wrote: I think the most important concrete step is to find more reviewers, which is already in the document. As to how to do that, I'm not sure. -- Andrei To be blunt, the vision (and goals in general) are kind of useless without a plan to achieve them.
Re: First dmd nightly shipping with dub
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?
Re: daffodil, a D image processing library
On Friday, 1 July 2016 at 01:24:55 UTC, rikki cattermole wrote: Doesn't use allocators or Manu's color work, yup yup not interested. Way to be a dismissive asshole. Let me rewrite that sentence for you: "Hey, nice work, we really need something like this. I'm a bit concerned about the GC usage though, have you checked out std.allocators or the proposed std.color? I think these will help make your library much faster."
Re: Release D 2.071.1
On Monday, 27 June 2016 at 22:11:53 UTC, Martin Nowak wrote: Glad to announce D 2.071.1. http://dlang.org/download.html This point release fixes a few issues over 2.071.0, see the changelog for more details. http://dlang.org/changelog/2.071.1.html -Martin Glad to see this out :)
Re: Release D 2.071.1
On Monday, 27 June 2016 at 23:15:06 UTC, Robert burner Schadek wrote: Awesome, releases are becoming more and more boring. I like it! I wouldn't call 1.0 * -1.0 == 1.0 boring!
Re: Beta D 2.071.1-b2
On Sunday, 29 May 2016 at 21:53:23 UTC, Martin Nowak wrote: Second beta for the 2.071.1 release. http://dlang.org/download.html#dmd_beta http://dlang.org/changelog/2.071.1.html Please report any bugs at https://issues.dlang.org -Martin This release would fix some pretty serious bugs. What's the holdup?
Re: Work in Amsterdam
On Wednesday, 15 June 2016 at 19:48:07 UTC, Dejan Lekic wrote: LinkedIn has the D Developer Network (DDN) group with 1900 members (at the moment of writing this post): https://www.linkedin.com/groups/3923820 I didn't know about this either. You should make a separate announce post about this.
Re: Beta D 2.071.1-b2
On Sunday, 29 May 2016 at 21:53:23 UTC, Martin Nowak wrote: Second beta for the 2.071.1 release. http://dlang.org/download.html#dmd_beta http://dlang.org/changelog/2.071.1.html Please report any bugs at https://issues.dlang.org -Martin 2.072 is getting rather long in the tooth: https://github.com/dlang/phobos/blob/master/changelog.dd. I think that's the largest change log for Phobos I have seen. When are you planning on branching master?
Re: The Official D Blog is Live
On Friday, 3 June 2016 at 19:33:31 UTC, Mike Parker wrote: so if you have any suggestions fire away. Two things I noticed: 1. The site doesn't gzip its responses. This can lead to a 30%-40% reduction in total page size if used. 2. The server isn't using Wordpress' custom server error pages. Also, one suggestion I have is to use a Wordpress plugin that caches the page results into static HTML. This saves the server regenerating the templates every page load, which requires a slow round trip to the database.
Re: The Official D Blog is Live
On Friday, 3 June 2016 at 19:33:31 UTC, Mike Parker wrote: The D Blog was born at DConf this year. With help from Jack Stouffer, it is now live at: http://dlang.org/blog/ IMO we should disable the comment section. Right now we are just asking for spam, and I don't think we want to be in the position of moderating each of these sections. Plus, all of the D tech discussions happen on reddit, HN, or on here, so I don't think we will be missing anything.
Re: Beta D 2.071.1-b2
On Sunday, 29 May 2016 at 21:53:23 UTC, Martin Nowak wrote: Second beta for the 2.071.1 release. http://dlang.org/download.html#dmd_beta http://dlang.org/changelog/2.071.1.html Please report any bugs at https://issues.dlang.org -Martin Please consider pulling https://github.com/dlang/phobos/pull/4401
Re: D's Auto Decoding and You
On Thursday, 2 June 2016 at 21:21:50 UTC, jmh530 wrote: I was a little confused by something in the main autodecoding thread, so I read your article again. Unfortunately, I don't think my confusion is resolved. I was trying one of your examples (full code I used below). You claim it works, but I keep getting assertion failures. I'm just running it with rdmd on Windows 7. import std.algorithm : canFind; void main() { string s = "cassé"; assert(s.canFind!(x => x == 'é')); } Your browser is turning the é in the string into two code points via normalization whereas it should be one. Try using \u00E9 instead.
Re: D's Auto Decoding and You
On Wednesday, 18 May 2016 at 22:23:45 UTC, jmh530 wrote: Is this true of all @property functions? No, this is purely a range thing where it's legal to have your front be a public member variable rather than a getter function. Should this be noted in the spec? While somewhat supported in the language, at the end of the day ranges are library types, so no. Should it be an error? No, people's code will error if they try to call a non callable anyway.
Re: D's Auto Decoding and You
On Wednesday, 18 May 2016 at 20:10:09 UTC, Jonathan M Davis wrote: At this point, if anyone ever calls front with parens, they're doing it wrong. $ cd ~/dlang/phobos && grep -r "\.front()" * | wc -l 3 Not bad. One is commented out and the other two look intentional.
Re: D's Auto Decoding and You
On Tuesday, 17 May 2016 at 16:24:31 UTC, jmh530 wrote: On Tuesday, 17 May 2016 at 14:06:37 UTC, Jack Stouffer wrote: http://jackstouffer.com/blog/d_auto_decoding_and_you.html Based on the recent thread in General, I wrote this blog post that's designed to be part beginner tutorial, part objective record of the debate over it, and finally my opinions on the matter. I probably would have preferred this split up into two parts with one on the tutorial and one on the record of the debate. It seems to focus more on the debate. That wasn't my intent. I wanted the debate to be a lens into a discussion of the technical merits and demerits of auto decoding. I have reworded some of the article in order to reflect this. Maybe you could get add a section that was like "for THIS type of string, do X for performance" with clear explanations of why that is the best way and why other ways will be slower. Then, you can have other sub-sections for "for THAT type of string, do Y for performance." You have some of this detail in there, but it's organized more with respect to the context of the debate, I think. I will add this, thanks.
Re: D's Auto Decoding and You
On Tuesday, 17 May 2016 at 14:44:06 UTC, Steven Schveighoffer wrote: ... Thanks, fixed all issues. Like the article, pretty much sums up my thoughts too. Thanks!
Re: D's Auto Decoding and You
On Tuesday, 17 May 2016 at 14:16:48 UTC, Steven Schveighoffer wrote: Starting to read it, see errors in your examples: is(s[0] == immutable char) -> is(typeof(s[0]) == immutable(char)) is(s.front == dchar) -> is(typeof(s.front()) == dchar) Thanks, fixed.
D's Auto Decoding and You
http://jackstouffer.com/blog/d_auto_decoding_and_you.html Based on the recent thread in General, I wrote this blog post that's designed to be part beginner tutorial, part objective record of the debate over it, and finally my opinions on the matter. When I first learned about auto-decoding, I was kinda miffed that there wasn't anything in the docs or on the website that went into more detail. So I wrote this in order to introduce people who are getting into D to the concept, it's benefits, and downsides. When people are confused in Learn why typeof(s.front) == dchar then this can just be linked to them. If you think there should be any more information included in the article, please let me know so I can add it.
Re: Beta D 2.071.1-b1
On Sunday, 15 May 2016 at 04:40:21 UTC, Martin Nowak wrote: First beta for the 2.071.1 point release. A few issues remain to be fixed before the next beta. http://dlang.org/download.html#dmd_beta http://dlang.org/changelog/2.071.1.html Please report any bugs at https://issues.dlang.org -Martin This should probably be stalled until https://github.com/dlang/dmd/pull/5781 is pulled.
Re: The D language online tour - tour.dlang.org
On Monday, 16 May 2016 at 18:02:29 UTC, Andrei Alexandrescu wrote: This is great work, thanks! Please announce in social media as well! -- Andrei Reddit: https://www.reddit.com/r/programming/comments/4jn6ks/the_online_d_language_tour/
Re: GSoC 2016 - Precise GC
On Tuesday, 3 May 2016 at 16:15:27 UTC, Jeremy DeHaan wrote: I agree, but a precise heap scan should be the easiest part of this project. Rainer Schuetze has already implemented this and presented it at a dconf a few years ago(2013?). My plan is to use that since I know it works, and that frees up my time to focus on pretty much everything else. I don't remember all the details, but I'm pretty sure that Rainer, or maybe someone else, was talking about how a precise GC is not completely possible in D because D has unions.
Re: Release D 2.071.0
On Monday, 2 May 2016 at 16:47:13 UTC, Márcio Martins wrote: with 2.070.2: real0m9.775s user0m9.036s sys 0m0.700s with 2.071.0: real0m45.011s user0m41.760s sys 0m3.144s Wow, that's pretty awful. Have you tried using digger to find out what caused the slow down?
Re: Release D 2.071.0
On Tuesday, 5 April 2016 at 22:43:05 UTC, Martin Nowak wrote: Glad to announce D 2.071.0. http://dlang.org/download.html This release fixes many long-standing issues with imports and the module system. See the changelog for more details. http://dlang.org/changelog/2.071.0.html -Martin Reddit: https://www.reddit.com/r/programming/comments/4dj84l/d_2071_has_been_released_long_standing_import/
Re: Units of Measurement Library: units-d
On Thursday, 31 March 2016 at 23:58:54 UTC, Nordlöw wrote: I've put David Nadlinger work together with my tweaks on top at https://github.com/nordlow/units-d to make it easier to experiment with. PR are very welcome. Nice work. I have yet to play around with it, but this is definitely going to need pre-made symbols for the United States customary system like SI has before it goes into Phobos.
Re: DConf 2016 announces programme, general registration opened thrugh April 22
On Tuesday, 29 March 2016 at 04:42:17 UTC, Dicebot wrote: I am not sure this has much value. The main benefit of live stream is that everyone can ask questions online and those will be forwarded to speakers. Isn't it better to simply wait for recorded high quality videos otherwise? P.S. devs from Europe did indeed have to stay awake through the night to watch previous dconfs ;) If you're going to live stream it, can you do it through Twitch so it's archived for a couple of days for people who can't stay up?
Re: Blog article on new import changes
On Tuesday, 29 March 2016 at 15:25:27 UTC, Steven Schveighoffer wrote: I anticipate 2.071.0 is going to cause a lot of deprecation messages and strange errors to occur, due to the fixes of very long-standing import bugs. I wrote a blog post (actually my first ever) on this, let me know what you think (and please, any clarifications/errors, let me know): http://www.schveiguy.com/blog/2016/03/import-changes-in-d-2-071/ This is an informative article, good job. Here are some notes I jotted down when reading it In the newest version of D upcoming, several changes have been made to the import system, including fixes for 2 of the oldest bugs in D history. Grammatically, it's redundant to put "upcoming" where it is; numbers under 20 are typically written with their name. However, until the fix was rendered, these module symbols were imported as if they were marked public. This sentence is redundant. This determines where the problem lies. This sentence is also redundant.
Re: D Profile Viewer
On Monday, 28 March 2016 at 23:43:51 UTC, Andrew wrote: On Saturday, 26 March 2016 at 03:41:14 UTC, Jack Stouffer wrote: If I could make one suggestion, this should be added to dub as an executable, so I can do dub fetch d-profile-viewer dub run d-profile-viewer Done! Works like a charm :)
dateparser hits 1.0
A little while ago, I wrote about a library I was writing to parse strings and return SysTime's, http://forum.dlang.org/post/odowolmiykkdigfit...@forum.dlang.org Well, that library has reached 1.0! https://github.com/JackStouffer/date-parser I'm quite happy with it; it's reasonably fast for what its doing, it has very few GC allocations, it supports std.allocator's theAllocator, and it supports range inputs. On average, it's about 10x faster than the Python version when compiled with LDC.
Re: Article on Introspective programming
On Monday, 28 March 2016 at 12:47:02 UTC, Nicholas Wilson wrote: http://thewilsonator.github.io/update/2016/03/28/better-vulkan-bindings.html I would like some feedback before this is posted to reddit. Come to think of it, putting the project on github would be a good idea, but unfortunately I won't have the time for at least a week. Oh well. Comments and suggestions appreciated. Nic Great article, some points I jotted down while reading: * I would emphasize the fact that D has no C translation layer a little more, something like "because D uses the C memory model ..." * Why do you use pre tags for numbered and bulleted lists? Use the native HTML tags instead * I would wrap the code in text in tags
Re: D Profile Viewer
On Thursday, 24 March 2016 at 20:34:07 UTC, Andrew wrote: Hi I wrote a program to turn the non-human-readable trace.log into an interactive HTML file that can be used to help profile a D program. Its here: https://bitbucket.org/andrewtrotman/d-profile-viewer There's also a readme that (hopefully) explains how to use it. Please let me know if you find any bugs. Andrew. Awesome work. If I could make one suggestion, this should be added to dub as an executable, so I can do dub fetch d-profile-viewer dub run d-profile-viewer
Re: New Article: My Experience Porting Python Dateutil's Date Parser to D
On Wednesday, 9 March 2016 at 21:55:23 UTC, Jack Stouffer wrote: The code and docs can be found here: https://github.com/JackStouffer/date-parser Quick update: all dateutil tests are now passing. It can how parse just about any date format you can throw at it :)
Re: New Article: My Experience Porting Python Dateutil's Date Parser to D
On Wednesday, 9 March 2016 at 22:12:42 UTC, Walter Bright wrote: I haven't read the article yet, but you'll get more interest by putting a summary as the first comment on reddit. Thanks for the advice, I think it caused more people to read it. Also, I forgot to mention in the article that the unit tests with coverage reports enabled run in 110ms. I love fast tests :)
Re: New Article: My Experience Porting Python Dateutil's Date Parser to D
On Wednesday, 9 March 2016 at 23:31:04 UTC, Ola Fosheim Grøstad wrote: On Wednesday, 9 March 2016 at 22:17:39 UTC, H. S. Teoh wrote: system for my personal projects), I can totally sympathize with the annoyances of using a dynamically-typed language, as well as dodgy iterator designs like __next__. (I've not had to deal with __next__ in Python so far, but *have* worked with C/C++ code that basically iterates that way, and it's not pretty.) What is problematic with __next__ (Py3) and next (Py2)? It's a pretty straight forward standard iterator design and quite different from the table pointers C++ uses. I explain my grievances in the article.
New Article: My Experience Porting Python Dateutil's Date Parser to D
Hello everyone, I have spent the last two weeks porting the date string parsing functionality from the popular Python library, dateutil, to D. I have written about my experience here: http://jackstouffer.com/blog/porting_dateutil.html The code and docs can be found here: https://github.com/JackStouffer/date-parser reddit: https://www.reddit.com/r/programming/comments/49qdpt/my_experience_porting_python_dateutils_date/ Let me know what you think about the article and the code. Thanks in advance.
Sublime Text 3 Gets Better D Support
Sublime Text is a very popular text editor, and for a while now it's had marginal D support. What has changed recently is updated syntax highlighting to support all the new keywords that have come in the last couple of years and UDAs https://github.com/sublimehq/Packages/commit/b9026cf6ab8ccd05e3704d21b2d5d5cc21450aca. Syntax highlighting was mostly based on D1 before, but now it supports every thing to pure and nothrow to correctly highlighting number literals with underscores. In order to use this, you can either wait until a version of sublime is released with these changes, or you can download the dev version here https://www.sublimetext.com/3dev, and then install the new packages as described here https://github.com/sublimehq/Packages#installation.
Re: Sublime Text 3 Gets Better D Support
On Wednesday, 27 January 2016 at 19:15:02 UTC, Damian wrote: Thank you, this is very much welcome! Wishlist: Will we see some dub support integration for building? I find when using rust the cargo build support is excellent, I wish we had this for D in sublime :) I actually didn't do this, I just complained on their issue tracker :) I use dub with sublime currently by using sublime's custom build system. Just go to "Build System" under tools, click new build system, and add in the following { "cmd": ["dmd", "-g", "-debug", "$file"], "file_regex": "^(.*?)\\(([0-9]+),?([0-9]+)?\\): (.*)", "selector": "source.d", "path": "/usr/bin:/usr/local/bin", "variants": [ { "name": "Run", "cmd": ["rdmd", "-g", "-debug", "$file"] }, { "name": "unittest", "cmd": ["rdmd", "-g", "-debug", "-unittest", "$file"] }, { "name": "dub", "working_dir": "$project_path", "cmd": ["dub"] } ] } Now in your D project, select the build system you just created, click shift command B, choose dub, and then command B, and now your building with dub.
Re: Vision for the first semester of 2016
On Monday, 25 January 2016 at 02:37:40 UTC, Andrei Alexandrescu wrote: Hot off the press! http://wiki.dlang.org/Vision/2016H1 -- Andrei My biggest issue with these documents is that they have good ideas but rarely have plans to achieve them. As a consequence, most of these documents say how half or more of the previous goals were not achieved. I believe the best way to fix this is to simply have more focus. Have one large goal that can be broken down into smaller subsets, e.g. "2016 will be the year of a GC free Phobos". Something that has a very clear way of quantifying its success and a clear path to that goal. Not that that the other things are not important, but if you constantly find yourself failing to meet your goals, the only rational option is to become more realistic in your plans.
Re: Bruce Eckel is evaluating languages
On Friday, 22 January 2016 at 20:19:55 UTC, Ali Çehreli wrote: https://www.reddit.com/r/programming/comments/426pwq/a_language_is_more_than_a_language/ Would someone from the D community add D to his project: http://bruceeckel.github.io/Language-Evaluation-Checklist/ Ali Meh. Doesn't exactly look like a popular initiative; currently it has less than 10 stars on GitHub.
Re: Flipboard collection of D articles
On Friday, 8 January 2016 at 08:43:52 UTC, florin wrote: So if there are any Flipboard users around interested in adding stuff there, please let me know and I will invite you to manage the said collection. Sure, I'm @jackstouffer on flipboard.
Re: Three Cool Things about D
On Friday, 8 January 2016 at 00:32:05 UTC, Rory McGuire wrote: On Mon, Dec 28, 2015 at 5:24 PM, Rory McGuirewrote: On 27 Dec 2015 6:25 PM, "Andrei Alexandrescu via Digitalmars-d-announce" < digitalmars-d-announce@puremagic.com> wrote: > > On 12/27/15 1:27 AM, Rory McGuire via Digitalmars-d-announce > wrote: [snip] >> Vibe.d had a template engine called diet which is almost >> like Jade. It is also completed so you might prefer that as >> an example. > > > Either or both would be awesome to express with Pegged. -- > Andrei > I'm working on the output part now while it's the holidays. Will share once I've got my test template translating to html as a demo. A little teaser, this is the output of the app and runtime Can you post all of the D code on github as well, seeing as the forum strips your code formatting, making it very hard to read.
Re: Using D and std.ndslice as a Numpy Replacement
On Monday, 4 January 2016 at 02:01:05 UTC, Ilya wrote: Please add links to 1. Mir: http://code.dlang.org/packages/mir 2. Documentation: http://dlang.org/phobos-prerelease/std_experimental_ndslice.html 3. DlangScience example Thanks! -- Ilya Updated. I also changed the example slightly from the DlangScience example by increasing the array size because some people on HN were complaining that the size of the data wasn't large enough for the benchmark to be meaningful.
Re: Using D and std.ndslice as a Numpy Replacement
On Monday, 4 January 2016 at 01:09:30 UTC, Ilya wrote: To be clear: there is NO data in Article example. Only CPU registers are used. It is not fair. -- Ilya Ok, I see were I made the mistake, I apologize. I believed that since I was only testing the np.mean line of code, that the lazy generation of the D in the D version would have no effects on the comparison. But I forgot the fact that the lazy generation would mean that no memory needed to be accessed in the D code and therefore it's not apples to apples with the Numpy code. Thank you for clarifying this, I will update the article.
Re: Using D and std.ndslice as a Numpy Replacement
On Monday, 4 January 2016 at 00:24:51 UTC, David Nadlinger wrote: On Sunday, 3 January 2016 at 18:56:07 UTC, Jack Stouffer wrote: I still have to disagree with you that the example I submitted was fair. Accessing global memory in D is going to be much slower than accessing stack memory, […] What leads you to this belief? (Beyond cache locality considerations, which are not so important if the data is large.) The example in the article and the example I submitted to DlangScience/examples have very different speeds: https://github.com/DlangScience/examples/blob/master/mean_of_columns.d Article example: 5 µs DlangScience example: 145 µs Both when compiled with LDC
Re: Using D and std.ndslice as a Numpy Replacement
On Sunday, 3 January 2016 at 00:17:23 UTC, Ilya Yaroshenko wrote: On Sunday, 3 January 2016 at 00:09:33 UTC, Jack Stouffer wrote: On Saturday, 2 January 2016 at 23:51:09 UTC, Ilya Yaroshenko wrote: This benchmark is _not_ lazy, so ndslice faster than Numpy only 3.5 times. I don't know what you mean here, I made sure to call std.array.array to force allocation. In the article: auto means = 100_000.iota < 100_000.iota is lazy range .sliced(100, 1000) .transposed .map!(r => sum(r) / r.length) .array; < allocation of the result In GitHub: means = data < data is allocated array, it is fair test for real world .sliced(100, 1000) .transposed .map!(r => sum(r, 0L) / cast(double) r.length) .array; < allocation of the result -- Ilya I still have to disagree with you that the example I submitted was fair. Accessing global memory in D is going to be much slower than accessing stack memory, and sense most std.ndslice calculations are going to be on the stack, I believe my benchmark is indicative of normal use.
Using D and std.ndslice as a Numpy Replacement
http://jackstouffer.com/blog/nd_slice.html https://www.reddit.com/r/programming/comments/3z6f7a/using_d_and_stdndslice_as_a_numpy_replacement/
Re: Using D and std.ndslice as a Numpy Replacement
On Saturday, 2 January 2016 at 22:15:03 UTC, Ali Çehreli wrote: Broken link in "For a more in depth look at ranges, see The official D tutorial's section on ranges". Ali Fixed, thanks!
Re: Using D and std.ndslice as a Numpy Replacement
On Saturday, 2 January 2016 at 23:51:09 UTC, Ilya Yaroshenko wrote: This benchmark is _not_ lazy, so ndslice faster than Numpy only 3.5 times. I don't know what you mean here, I made sure to call std.array.array to force allocation.
Voting Open For std.experimental.ndslice
http://forum.dlang.org/post/yeebmehdqgqdfkzmz...@forum.dlang.org
Re: Testing Nightly Build Service
On Saturday, 12 December 2015 at 12:08:50 UTC, Martin Nowak wrote: As you might already know from the last sprint review (http://forum.dlang.org/post/56592679.3010604@dawg.) Does anyone who doesn't work on DMD read those? we've setup a server to build nightlies. The service is still in a test phase but seems to work steadily. You can try it using the install script curl -fsSL https://builds.dawg.eu/install.sh | bash -s dmd-nightly or by simply downloading the latest archive for your platform. https://builds.dawg.eu/dmd-nightly/ Thanks for this Martin! Discussion on reddit: https://www.reddit.com/r/programming/comments/3wj1f7/d_nightly_builds_now_available/