BEERCONF! T-shirts
At the last Beerconf, there was a discussion about creating some Beerconf t-shirts. Now, thanks to Iain Buclaw, we've got BEERCONF! shirts in our DLang Swag Emporium. The BEERCONF! category isn't showing up right now, but when it eventually does, you can find it on the home page here: https://www.zazzle.com/store/dlang_swag?rf=238129799288374326 In the meantime, here are some direct links to the t-shirts: Light Colors https://www.zazzle.com/z/ak35l96q?rf=238129799288374326 Dark Colors https://www.zazzle.com/z/ahx7asux?rf=238129799288374326 The D Language Foundation will receive 18% of every sale, plus a referral fee if you go through these links. The link in the sidebar on the D Blog will also give us the referral fees.
Re: D Language Foundation Monthly Meeting -- June 2021
On Tuesday, 29 June 2021 at 21:35:56 UTC, matheus wrote: Was the meeting recorded? Where can we watch? Matheus. No, it was not recorded. And no, we aren't going to start recording them.
D Language Foundation Monthly Meeting -- June 2021
The monthly DLF meeting this month took place on June 25. It lasted a little over an hour-and-a-half. We discussed a number of topics which, as always, led to notes for further discussion in future meetings. Walter, Atila, Andrei, Razvan, Max, and I attended (no I did not leave out Ali by mistake like I did last month; he really couldn't be there this time). The topics that led to some sort of actionable result: --- The vision document is almost ready. I'm currently waiting for a description of the ImportC endgame, after which I'll work with Razvan to flesh out the full document and publish it somewhere visible (dlang.org or the wiki, perhaps). Prior to the meeting, there was some discussion among a few people regarding the strategy for Phobos v2 and work that had previously been done. At the moment, Andrei and Atila feel the previous work is not the right direction. Atila is going to experiment with an approach he favors, though some potential issues were raised at the meeting. We'll see what his experiment turns up. The PR for the forking GC that Francesco Mecca worked on for SAoC 2018 is still open. We would like to get it merged and have someone in mind to champion it. I will ask this person if he is interested and able to take on the task. (No names unless he accepts.) https://github.com/dlang/druntime/pull/2604 We had a discussion about stack allocation limits, mostly arising from this Bugzilla issue: https://issues.dlang.org/show_bug.cgi?id=17566 As per Walter's recent comment in that thread, he asserts that stack allocations beyond 4k should be rejected. Max's implementation of the Named Arguments DIP is coming along. Walter expressed that the final implementation should not be independent of struct initializers, i.e., one should be lowered to the other, or they should share the same implementation. Razvan is almost ready to start testing the Bugzilla gamification system. We're looking to launch it in late July or early August, at which point we are looking to have a DConf Sprint so that we can award prizes to some of our bugfixers at DConf Online in November. At DConf Online, we'll have keynotes from Walter and Atila as expected, along with an Ask us Anything! session. I've encouraged the rest of the DLF team to consider submitting talks this year. We have very nearly hit 1000 subscribers on YouTube. We will do so at some point in the next few months, at which time we'll be eligible to apply to monetize the channel (we already meet the watch hours requirement). I anticipate that, over time, this will be a nice way to raise money. I really want to start publishing more content on our channel outside of DConf. You may have heard me mention before that I want to start a 'D Community Talks' playlist (where we will offer a $300 bounty for quality content from community members, as we do for guest posts on the D Blog). I've also asked the DLF team to come up with other ideas for content (interviews, developer vlogs, etc). --- That's pretty much it. As I said above, the discussion (as usual) did branch into topics that didn't result in anything actionable, but some of it may well in the future. I don't want to say much about those topics unless and until they become concrete targets of focus. For now, they're essentially just brainstorming. Our next meeting will be on the 4th Friday of July. This will be a quarterly meeting in which representatives from the industry will participate. Those meetings begin by giving the industry folks the floor, after which the DLF folks (and any of the industry reps who'd like to) hang around for the monthly DLF meeting.
D News Roundup on the Blog: SAoC, DConf Online, Compiler Releases
I've posted a collective announcement of recent big happenings in D Land with all the relevant links. The SAoC 2021 and DConf Online 2021 pages are live with the information you need to submit proposals. Looking forward to see what comes around! The blog: https://dlang.org/blog/2021/06/18/d-news-roundup-saoc-2021-dconf-online-2021-new-compiler-releases/ /r/programming: https://www.reddit.com/r/programming/comments/o2ogsl/dlang_20970_dconf_online_2021_announced/ /r/d_language: https://www.reddit.com/r/d_language/comments/o2omsl/d_news_roundup_saoc_2021_dconf_online_2021_new/ SAoC 2021 info: https://dlang.org/blog/symmetry-autumn-of-code/ DConf Online 2021 https://dlang.github.io/dconf.org/2021/online/index.html Note that I'm currently waiting for dconf.org to be redirected to our GitHub pages URL.
DConf Online & Symmetry Autumn of Code 2021
Symmetry has confirmed: we are doing SAOC 2021 and it kicks off on September 15. And I can confirm that DConf Online 2021 is happening in November. I'll be formally announcing both on the D Blog soon, with dates, deadlines, and details. I'm announcing informally here first primarily because I want to encourage everyone to start thinking about the types of projects that would be good for SAOC and submitting ideas in our Projects repository before the announcement next week: https://github.com/dlang/projects/issues We have a few there already, but we can always use more. The SAOC work period runs for four months, during which participants are expected to work at least 20 hours per week on their projects. Please keep that in mind when you submit your ideas. You do not need to be a student to participate in SAOC. Students will be preferred during selection, but applications are open to everyone. If you would like to participate, now is the time to start thinking about the kind of project you'd like to work on and find yourself a mentor. If you are interested in making yourself available as a SAOC mentor, please leave a comment on the issues for the projects (in the repository linked above) on which you'd be inclined to do so. If you'd like to make yourself generally available as a mentor, please email me directly at aldac...@gmail.com and let me know. Each mentor is awarded $500 at the end of the event, courtesy of Symmetry Investments. I encourage everyone to think about submitting a talk or livecoding proposal for DConf Online. We're open to accepting anything related to the D programming language or general computer science topics. Submission details will be provided in the upcoming blog announcement. For the past couple of weeks, I've been editing the Q & A videos from last year's conference to cut out the dead space and irrelevant chatter. That has resulted in much shorter, uninterrupted videos. I still have three more to go. Those that I've already published have (v2.0) in the title. I've also added timecodes in the description of the new videos so that YouTube will show chapters, or bookmarks, at the bottom of the player frame. It's taking me several hours to work through each video, so I don't expect to have the remainder published until the end of next week at the earliest. The DConf Online 2020 Q & A playlist is here: https://www.youtube.com/watch?v=4G1FoocVVPY=PLIldXzSkPUXX0PcnTlv175rEyfH66yaoI If you missed the talks last year, they are all here (along with the 'Ask us Anything' with Walter and Atila, and Adam's livecoding session): https://www.youtube.com/watch?v=XQHAIglE9CU=PLIldXzSkPUXWsvFA4AuawPoMnq9Bh1lIZ #dconf #saoc
Re: D Language Foundation Monthly Meeting Summary
On Wednesday, 2 June 2021 at 11:10:36 UTC, Dukc wrote: Phobos v2 is an official plan? That was news for me! Any chance to get a glimpse of what's planned for it? The overall goal is that it doesn't replace the current Phobos, but sits alongside it. Changed/improved/new functionality goes in the std.v2 namespace (or whatever it looks like in the end) and you can import that alongside existing std packages. Andrei has talked about it a little here in the forums, and Steve did some preliminary work a while back. Beyond that, I have no details about plans. We'll have more after the workgroup gets going.
From the D Blog: Driving with D
Dylan Graham writes about his experience using D in a microcontroller project and why he chose it. Does anyone know of any similar projects using D? I don't. This may well be the first time it's been employed in this specific manner. The blog: https://dlang.org/blog/2021/06/01/driving-with-d/ Reddit: https://www.reddit.com/r/programming/comments/nps6k5/driving_with_dlang/
DIP 1038--@nodiscard--Formal Assessment Begins
I have just handed off DIP 1038, "@nodiscard", to Walter and Atila for their final verdict. They will have 30 days to reach a decision, ask for changes, or otherwise inform us of the status of the DIP. You can read the current revision here: https://github.com/dlang/DIPs/blob/0f872db7c0729441d6b7d09b0a55992080ad67f4/DIPs/DIP1038.md
Re: D Language Foundation Monthly Meeting Summary
On Friday, 28 May 2021 at 14:56:08 UTC, Mike Parker wrote: We've just completed our monthly meeting for the month of May 2021. One decision we made is to start providing summaries of the topics discussed. Hence this forum post. The participants: Walter, Atila, Andrei, Razvan, Max, and me. And Ali!
D Language Foundation Monthly Meeting Summary
We've just completed our monthly meeting for the month of May 2021. One decision we made is to start providing summaries of the topics discussed. Hence this forum post. The participants: Walter, Atila, Andrei, Razvan, Max, and me. ### Goals & Tasks The primary topic on our agenda for this meeting was a goal-oriented task list. In place of the old vision documents, we want to start maintaining a list of our current major long-term goals and some more minor short-term goals, broken down into specific tasks. This serves both as the current vision and as a task list for community members looking to make an impact with their contributions. For example, Bugzilla issues that fall under a goal will be labeled as such, so contributors can more effectively focus their attention. The list will also be used to guide some of the work our new strike teams will be doing. We've got a preliminary list of high-level goals that we will flesh out with specific tasks over the next couple of weeks. For example, major long-term goals are memory safety (e.g., specific bugs, fully enabling DIP 1000 support) and Phobos v2. There were other goals discussed, such as implementing named arguments, improving compile-time introspection, improving Phobos @safety, and more. I don't know yet what the initial version of the final list will look like, but I hope to publish it in the next two or three weeks. ### Error Messages We discussed how to improve error messages. Walter exhorts everyone to please raise a Bugzilla issue for specific error messages you encounter that you think need improvement. Walter also said he is open to accepting the implementation of a command-line switch that enables URLs in error messages to provide more information. ### Next Meeting Our next monthly meeting will take place on June 25th. We haven't yet set the agenda, but a portion of it will be devoted to following up on some of the topics discussed in today's meeting.
DIP 1036--String Interpolation Tuple Literals--Has Been Withdrawn
The authors of DIP 1036, "String Interpolation Tuple Literals", have chosen to withdraw it from consideration in deference to an alternative proposal currently being drafted here: https://github.com/John-Colvin/YAIDIP From the DIP review process documentation: Unlike Abandoned DIPs, a Withdrawn DIP cannot be revived without the DIP manager's approval. A DIP author will have a specific reason for withdrawing from the process, and that reason might preclude further consideration of the DIP. For example, a DIP that was withdrawn because it received an overwhelmingly negative response should be rewritten and submitted as a new proposal rather than revived in its original form. If the DIP manager does allow a Withdrawn DIP to be revived, it must begin the review process anew from the first round of Community Review. https://github.com/dlang/DIPs/blob/master/docs/process-reviews.md#withdrawn-and-superseded-dips The DIP's new home is here: https://github.com/dlang/DIPs/blob/master/DIPs/other/DIP1036.md
Re: From the D Blog -- Interfacing D with C: Strings Part One
On Tuesday, 25 May 2021 at 00:58:31 UTC, Steven Schveighoffer wrote: On 5/24/21 8:38 PM, Mike Parker wrote: OK, I'm just concerned people will see the pattern: ```d somecfunc(str.toStringz); ``` and think that's the end of it. Yeah. Good point. I've updated the post.
Re: From the D Blog -- Interfacing D with C: Strings Part One
On Monday, 24 May 2021 at 16:16:53 UTC, Steven Schveighoffer wrote: Nice article! Thanks! Note that there is a huge pitfall awaiting you if you use `toStringz`: garbage collection. You may want to amend the article to identify this pitfall. And I'm not talking about requiring `@nogc`, I'm talking about the GC collecting the data while C is still using it. In your example: ```d puts(s1.toStringz()); ``` This leaves a GC-collectible allocation in C land. For `puts`, it's fine, as the data is not used past the call, but in something else that might keep it somewhere not accessible to the GC, you'll want to assign that to a variable that lasts as long as the resource is used. That's what I'm referring to in the conclusion where I say this about what's going to be in Part Two: how to avoid a potential problem spot that can arise when passing GC-allocated D strings to C I'll cover approaches to maintaining a reference, like `GC.addRoot`, and emphasize that it applies to any GC-allocated memory, not just strings.
Re: From the D Blog -- Interfacing D with C: Strings Part One
On Monday, 24 May 2021 at 15:10:46 UTC, sighoya wrote: There are at least two more posts worth of information to go into on this topic, but everything in this post is enough to cover many use cases of D to C string interop. Which posts did you think of? I describe them in the Conclusion: In Part Two, we’ll look at how mutability, immutability, and constness come into the picture, how to avoid a potential problem spot that can arise when passing GC-allocated D strings to C, and how to get D strings from C strings. We’ll save encoding for Part Three.
Re: From the D Blog -- Interfacing D with C: Strings Part One
On Monday, 24 May 2021 at 15:03:20 UTC, zjh wrote: I always think there is something wrong with the JS of ` D blog site`. I can't use chrome to open it. I'm looking at it in Chrome right now. Are you saying it doesn't open at all for you or there are rendering issues, or...?
From the D Blog -- Interfacing D with C: Strings Part One
The latest post in the D and C series dives into the weeds of D and C strings: how they're implemented, when you need to NUL-terminate your D strings and when you don't, and how the storage of literals in memory allows you to avoid NUL termination in one case you might not have considered and another case that you shouldn't rely on but can in practice with the current compilers. There are at least two more posts worth of information to go into on this topic, but everything in this post is enough to cover many use cases of D to C string interop. The blog: https://dlang.org/blog/2021/05/24/interfacing-d-with-c-strings-part-one/ Reddit: https://www.reddit.com/r/programming/comments/njyf76/interfacing_d_with_c_strings_part_one/
A Pull Request Manager's Perspective
Razvan Nitu, one of the foundation's two Pull Request Managers funded by Symmetry Investments, talks about the work he's been doing and two initiatives intended to motivate contributions to the core D projects. https://dlang.org/blog/2021/05/18/a-pull-request-managers-perspective/ I've also shared it to the D subreddit if anyone wants to follow or participate in any discussion that arises there: https://www.reddit.com/r/d_language/comments/nf9z1e/a_pull_request_managers_perspective/
News Roundup on the D Blog
This news round-up serves as the "public-facing" announcement of the latest D release, a hint at the upcoming LDC beta, and word on GDC progress. I've also included the formal announcement of the SAOC 2020 results, and a reminder about a couple of Github repositories where anyone looking to sharpen their D skills can go for some ideas, wether they're looking for a major project or some simple tasks to fill an afternoon. The blog: https://dlang.org/blog/2021/03/24/d-2-096-0-released-and-other-news/ Reddit: https://www.reddit.com/r/programming/comments/mc45ob/dlang_20960_released/
Re: On the D Blog--Symphony of Destruction: Structs, Classes, and the GC
On Thursday, 18 March 2021 at 12:27:56 UTC, Petar Kirov [ZombineDev] wrote: Just implementation deficiency. I think it is fixable with some refactoring of the GC pipeline. One approach would be, (similar to other language implementations - see below), that GC-allocated objects with destructors should be placed on a queue and their destructors be called when the GC has finished the collection. Afterwards, the GC can release their memory during the next collection. As I understand, finalizers in D are run because the GC needs more memory *now*. Deferring release of memory until the next collection would defeat the purpose. We would need to decouple collection cycles from allocation. Am I missing something?
Re: On the D Blog--Symphony of Destruction: Structs, Classes, and the GC
On Thursday, 18 March 2021 at 08:15:01 UTC, Per Nordlöw wrote:
In the mean time a good rule of thumb is to qualify all class
destructors as @nogc. I suggest you add this advice to the
article, Mike.
I actually don't agree with that. I'll be discussion the solution
in the next article:
if(!GC.inFinalizer) {
...
}
It's perfectly fine to perform GC operations in destructors when
they aren't invoked by the GC.
GSOC and SAOC Projects List
Some of you will have already heard that we didn't make it into GSoC 2021. Every year Google receives over 500 organization applications, but they can only accept ~200. I have no insights into their decision process, but I do believe our application was stronger this year than it was when we were last accepted in 2019. Given that we've missed out on two in a row, I expect the odds will begin to favor us getting in again next year or the year after. That said, it surely won't hurt our chances to have a larger selection of projects that students can choose from. Such a pool of projects also helps us if and when we have another SAOC event. So I just want to remind everyone that the project ideas repository is there year-round. Anytime you have an idea for a D project that would benefit the ecosystem, please visit the repository and submit your idea: https://github.com/dlang/projects/issues When the time comes for GSoC or SAOC (Symmetry Autumn of Code), someone will go through and tag projects that appear suitable for the event. And I should point out, for anyone looking for a way to contribute to the D ecosystem, these ideas aren't exclusively for the two events. Everyone is welcome to come and take one of these on. Just please be sure to leave a comment on the appropriate issue that you are doing so. It will also be great to have a pool of people who are willing to work as mentors during the events. Anyone willing to mentor a specific project in the repository should leave a comment indicating their interest. And please, if you see someone else has already done so, leave a comment anyway. There's no guarantee that any given mentor will be available when the event comes around, so having some depth to the list is a good thing. If you're willing to be generally available as a mentor, please drop a line to soc...@dlang.org to let us know if you're interested in mentoring for either one or both of GSoC and SAOC and (broadly) what kinds of projects you're comfortable with. These steps will help prevent us from needing to scrounge around at the last minute for more projects and mentors. It will also allow us to better show in our GSoC applications that we have a lot to be done and that we could really use the resources the event provides.
Google Summer of Code and Symmetry Autumn of Code Projects and Mentors
Some of you will have already heard that we didn't make it into GSoC 2021. Every year Google receives over 500 organization applications, but they can only accept ~200. I have no insights into their decision process, but I do believe our application was stronger this year than it was when we were last accepted in 2019. Given that we've missed out on two in a row, I expect the odds will begin to favor us getting in again next year or the year after. That said, it surely won't hurt our chances to have a larger selection of projects that students can choose from. Such a pool of projects also helps us if and when we have another SAOC event. So I just want to remind everyone that the project ideas repository is there year-round. Anytime you have an idea for a D project that would benefit the ecosystem, please visit the repository and submit your idea: https://github.com/dlang/projects/issues When the time comes for GSoC or SAOC, someone will go through and tag projects that appear suitable for the event. And I should point out, for anyone looking for a way to contribute to the D ecosystem, these ideas aren't exclusively for the two events. Everyone is welcome to come along and take one of these on. Just please be sure to leave a comment on the appropriate issue that you are doing so. It will also be great to have a pool of people who are willing to work as mentors during the events. Anyone willing to mentor a specific project in the repository should leave a comment indicating their interest. And please, if you see someone else has already done so, leave a comment anyway. There's no guarantee that any given mentor will be available when the event comes around, so having some depth to the list is a good thing. If you're willing to be generally available as a mentor, please drop a line to soc...@dlang.org to let us know if you're interested in mentoring for either or both GSoC and SAOC, and (broadly) what kinds of projects you're comfortable with. These steps will help prevent us from scrounging around at the last minute for more projects and mentors. It will also allow us to better show in our GSoC applications that we have a lot we need done and that we could really use the resources the event provides. I don't know if that will increase our chances, but it surely can't hurt.
DIP 1040--Copying, Moving, and Forwarding--Community Review Round 1 Begins
The first round of Community Review for DIP 1040, "Copying, Moving, and Forwarding", is now underway. Please discuss the DIP (its merits, its implementation, peripheral topics, etc.) in the Discussion Thread and save all review feedback (critiques on the content of the DIP: what to change, how to improve it, etc.) for the Feedback Thread. Discussion Thread: https://forum.dlang.org/post/ncoqnixvllbjsxdzb...@forum.dlang.org Feedback Thread: https://forum.dlang.org/post/axgfyrxvndxdmffkx...@forum.dlang.org Please note that this proposal was written and submitted as a draft PR by Walter *prior* to the decision last year that the language maintainers must find someone else to author their DIP ideas. He had two DIPs in Draft Review at the time, and we agreed in a Foundation meeting that they both should be subject to the new rule. So they have been sitting in the queue waiting for someone to take them on. Max Haughton was the first to express an interest in doing so. This DIP is now entirely his responsibility. He will decide if and how to revise it in response to feedback in the review process. He declined to make any changes to the DIP prior to launching this review round. The other DIP by Walter in need of a champion is a fairly simple one, "Evaluate Pure Functions with CTFE". Anyone interested in taking control of it, please email me at aldac...@gmail.com and we'll discuss it. You can find it at: https://github.com/dlang/DIPs/pull/177
Re: On the D Blog--Symphony of Destruction: Structs, Classes, and the GC
On Thursday, 4 March 2021 at 23:42:58 UTC, Dukc wrote: I don't understand this part. If an assert was failing, the program is going to terminate anyway, so InvalidMemoryOperationError is no problem. Well, it might obfuscate the underlying error if there is no stack trace, but banning `assert`ing in anything that could be called by a destructor sounds too drastic to me. Even the lowest level system code tends to contain asserts in D, at least in my codebase. If asserting is banned, destructors can do faily much nothing. I'd think it's much more practical to redefine the assert failure handler if InvalidMemoryOperationError due to a failed assert is a problem. Yes, this can be worked around. Passing -checkaction=C to the compiler will use the C assert handler and no exception will be thrown (which, IMO, should be the default behavior of asserts anyway). But even then, I believe as a general rule that any code which touches an assert has no place in a finalizer. And that's because asserts are inherently deterministic. A properly-written assert is used to verify an expectation that the program is in a specific state at a specific point in its execution. If the program is not in that state at that point, then we know we've got an error in our code. It's because of this determinism that we can remove asserts from released code and expect that nothing will break, and it's why we don't assert on conditions that are beyond our control (like user input). Because finalizers are non-deterministic, they kill that "at a specific point in the program's execution" part, rendering any asserts they touch unreliable. It is realistically possible that an assert invoked in a finalizer never triggers during development, then the program is released with asserts removed, and then it breaks out in the wild because a finalizer is invoked at a point when the program isn't in the expected state. This doesn't make *destructors* useless, but *finalizers* really are mostly useless most of the time, IMO. As D programmers, we need to consciously be aware of the distinction since the language isn't.
On the D Blog--Symphony of Destruction: Structs, Classes, and the GC
This post is 3+ years overdue. I initially put it off for the lack of a purpose-built tool in the language or the library to distinguish between normal destruction and finalization (when the GC is invoked by the destructor). After we got the `GC.inFinalizer` thing and having made a few stalled attempts to get the thing written, I finally sat down a couple of weeks ago and forced myself to finish it. The result is not what I had originally intended, as the topic turned out to be much more involved than I had realized. What was supposed to be one post very quickly became two, and now it looks like there will be at least four before I'm done. (I didn't even get to the GC.inFinalizer thing in this first post.) Object destruction in D has dark corners that I had never knew existed until recently, and I expect that as I experiment with them and talk with some battle-hardened warriors like Adam, I'll find myself with many more words to write on the topic. The blog: https://dlang.org/blog/2021/03/04/symphony-of-destruction-structs-classes-and-the-gc-part-one/ Reddit: https://www.reddit.com/r/programming/comments/lxkcxp/symphony_of_destruction_structs_classes_and_the/ The GC series to date: https://dlang.org/blog/the-gc-series/
Re: bindbc-lua 0.4.0 -- Lua 5.4, parameter names
On Thursday, 25 February 2021 at 19:28:43 UTC, Dennis wrote: On Friday, 19 February 2021 at 08:28:01 UTC, Mike Parker wrote: GitHub: https://github.com/BindBC/bindbc-lua/releases/tag/0.4.0 The link doesn't work because the tag lacks a 'v', should be: https://github.com/BindBC/bindbc-lua/releases/tag/v0.4.0 Thanks! Originally, I left the v off the tag, and of course that breaks in dub. I updated the tag yesterday and forgot to update this post.
DIP 1035--@system Variables--Community Review Round 2 Begins
The second round of Community Review for DIP 1036, "String Interpolation Tuple Literals", is now underway. Please discuss the DIP (its merits, its implementation, peripheral topics, etc.) in the Discussion Thread and save all review feedback (critiques on the content of the DIP: what to change, how to improve it, etc.) for the Feedback Thread. Discussion Thread: https://forum.dlang.org/post/flwbqmpcwenplqdof...@forum.dlang.org Feedback Thread: https://forum.dlang.org/post/eivezuohaejnvvlha...@forum.dlang.org
Re: I learned something new in D this week! (anonymous class rundown)
On Thursday, 18 February 2021 at 04:31:39 UTC, Adam D. Ruppe wrote: Would you like to know more? http://dpldocs.info/this-week-in-d/Blog.Posted_2021_02_15.html It's on /r/programming here: https://www.reddit.com/r/programming/comments/lnhuts/anonymous_classes_in_d/
bindbc-lua 0.4.0 -- Lua 5.4, parameter names
In the latest release of binbc-lua, I've added support for Lua 5.4. In recognition of the upcoming named argument support, I've decided to add parameter names to all of the C API function declarations in the BindBC packages. bindbc-lua 0.4.0 now has them, even for the function pointers in the dynamic binding. I've also fixed some minor bugs and cleaned up the README. I think at this point, the bindbc-loader package has proven stable long enough that I can declare a version 1.0.0. I'll do that in the near future and will follow it with 1.0.0 releases of all of my BindBC packages. bindbc-lua 0.4.0 can be found at GitHub: https://github.com/BindBC/bindbc-lua/releases/tag/0.4.0 code.dlang.org (not yet updated as I write this): http://bindbc-lua.dub.pm/
Re: DIP 1034--Add a Bottom Type (reboot)--Formal Assessment Concluded
On Tuesday, 16 February 2021 at 07:07:09 UTC, Mike Parker wrote: Congratulations to Dennis Korpel for a job well done, and thanks to everyone who provided feedback on this DIP from the Draft Review through to the Final Review. And here's the link: https://github.com/dlang/DIPs/blob/master/DIPs/accepted/DIP1034.md
DIP 1034--Add a Bottom Type (reboot)--Formal Assessment Concluded
When I emailed Walter and Atila to officially launch the Formal Assessment of DIP 1034, "Add a Bottom Type (reboot)", I expected it would be three or four weeks before I received their final decision. So I was surprised when Walter replied two days later with the following response: "Accepted with pleasure and enthusiasm. This is what DIPs should be like. I intuitively felt that a bottom type was right for D, but failed to express it in DIP1017. Dennis has done it right." Atila was on vacation at the time, but as soon as he got back he responded: "Seconded." Congratulations to Dennis Korpel for a job well done, and thanks to everyone who provided feedback on this DIP from the Draft Review through to the Final Review.
Re: Beerconf February 2021
On Sunday, 14 February 2021 at 00:54:41 UTC, superbomba wrote: On Saturday, 13 February 2021 at 20:48:53 UTC, Steven Schveighoffer wrote: ... Is it possible to rebroadcast live with YT for those who can't access the original site or app? What would be the point of that? You'd be unable to participate in the conversation.
SAOC 2020 Ends
The final Milestone for SAOC 2020 Ended on January 15. The two remaining students, Robert Aron and Adela Vais, had until the end of the month to submit their final reports. They did so, and the reports are now in the hands of the SAOC Committee, which this year consists of Atila Neves, John Colvin, and Robert Schadek. These three have the difficult task of deciding who should receive the final $1000 milestone payment and the free registration, travel, and lodging at the next real-world DConf. Both of the students impressed their mentors with their performance throughout the event and should be proud of what they achieved no matter the outcome. A big thanks to Razvan Nitu and Eduard Staniloiu for mentoring all of the SAOC students this year. We also want to thank all of the students who participated in SAOC 2020 and we look forward to seeing what their futures hold as members of the D community.
DIP 1038--@nodiscard--Final Review Begins
The Final Review for DIP 1038, "@nodiscard", has begun. The Final Review is the 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 when no revisions were made, it's a final opportunity to catch any problems that may have been missed before. Please discuss the features of the proposal (its merits, its implementation, peripheral topics, etc.) in the Discussion Thread and save all review feedback (critiques on the content of the DIP: what to change, how to improve it, etc.) for the Feedback Thread. Discussion Thread: https://forum.dlang.org/post/nfyfsmenjwzhbezff...@forum.dlang.org Feedback Thread: https://forum.dlang.org/post/ipfmxoimroobpzymr...@forum.dlang.org
DIP 1034--Add a Bottom Type (reboot)--Formal Assessment Begins
After a bit of delay, DIP 1034, "Add a Bottom Type (reboot)", is now in the hands of Walter and Atila for the Formal Assessment. We can expect to have a final decision or some other result by March 4. You can find the final draft of DIP 1034 here: https://github.com/dlang/DIPs/blob/1eb2f39bd5b6652a14ef5300062a1234ad00ceb1/DIPs/DIP1034.md
Re: DIP 1036--String Interpolation Tuple Literals--Community Round 2 Begins
On Wednesday, 27 January 2021 at 11:14:13 UTC, Petar Kirov [ZombineDev] wrote: Corrected links: Thanks. I had too many tabs open.
DIP 1036--String Interpolation Tuple Literals--Community Round 2 Begins
The second round of Community Review for DIP 1036, "String Interpolation Tuple Literals", is now under way. Please discuss the DIP (its merits, its implementation, peripheral topics, etc.) in the Discussion Thread and save all review feedback (critiques on the content of the DIP: what to change, how to improve it, etc.) for the Feedback Thread. Discussion Thread: https://forum.dlang.org/post/ucqyqkvaznbxkasvd...@forum.dlang.org Feedback Thread: https://forum.dlang.org/post/qglydztoqxhhcurvb...@forum.dlang.org
Re: Please Congratulate My New Assistant
On Monday, 18 January 2021 at 09:49:10 UTC, M.M. wrote: Is this (and the related PR people) a short-term initiative, or is the funding secured for a longer period? As far as I know this is long term.
Re: Please Congratulate My New Assistant
On Monday, 18 January 2021 at 13:08:58 UTC, Mike Parker wrote: On Monday, 18 January 2021 at 09:32:06 UTC, Imperatorn wrote: (Also, general question: Will the PR guys and Max be on Discord or Slack or will it be too much for them?) That's up to them, but I guess Max probably will be. I should clarify that I was referring to Discord. They're on Slack already.
Re: Please Congratulate My New Assistant
On Monday, 18 January 2021 at 09:32:06 UTC, Imperatorn wrote: (Also, general question: Will the PR guys and Max be on Discord or Slack or will it be too much for them?) That's up to them, but I guess Max probably will be.
Please Congratulate My New Assistant
Thanks once more to Symmetry Investments, we have a new paid staffer in the D Language Foundation family. Though I call him my "assistant", I can already see he will be more than that. He'll be taking some things off my shoulders, sure, but he also has ideas of his own to bring into the mix. Adding him to the team is certain to be a boon for the D community. So, a word of warning to those of you who haven't heard from me in a while pestering you for blog posts: get used to the name "Max Haughton". And congratulate him while you're at it!
Say Hello to Our Two New Pull-Request/Issue Managers
I'm very, very happy that I can finally announce the news. Some of you may recall the job announcements I put out on the blog back in September [1]. Symmetry Investments offered to fund one full-time, or two part-time, Pull Request Manager positions, the goal being to improve the efficiency of our process (prevent pull requests from stagnating for ages, make sure the right people see the PRs in need of more than a simple review, persuade the right people to help with specific Bugzilla issues, etc). Several people applied for the job, including some unknown in the D community. Ultimately, two people were selected: one to fill an administrative/managerial role, the other to fill a more technical role. Today I can tell you who they are. Please congratulate Andrew Edwards and Razvan Nitu on their new positions! They have already been on the job for several days and are eager to make a difference. Currently, their responsibilities are outlined here at: https://dlang.org/foundation/prman.html Please consider this a living document. We will amend and revise it as we learn more about what they and the community need for them to do this job right. I ask that everyone please give them time to settle in. I expect we'll hear from them once they have, with some details regarding how they'll perform their duties and any relevant information for contributors. Congratulations to Andrew and Razvan, and tremendous thanks to Symmetry for making this happen. [1] https://dlang.org/blog/2020/08/30/symmetry-investments-and-the-d-language-foundation-are-hiring/
Re: Release D 2.095.0
On Saturday, 2 January 2021 at 20:15:16 UTC, Martin Nowak wrote: Glad to announce D 2.095.0, ♥ to the 61 contributors. This release comes with a much improved C++ header generation, template instantiation traces for deprecations, module-level function conflict detection, and better compiler flag support in dub. http://dlang.org/download.html http://dlang.org/changelog/2.095.0.html -Martin Blog Post (including LDC beta news): https://dlang.org/blog/2021/01/11/a-new-year-a-new-release-of-d/ Reddit: https://www.reddit.com/r/programming/comments/kv2ug5/dlang_20950_released/
Re: Discussion Thread: DIP 1039--Static Arrays with Inferred Length--Community Review Round 1
On Thursday, 7 January 2021 at 21:26:28 UTC, Steven Schveighoffer wrote: Should this be on the announce forum? No it shouldn't. But by the time I realized it was, the discussion was well underway.
Re: Discussion Thread: DIP 1039--Static Arrays with Inferred Length--Community Review Round 1
On Thursday, 7 January 2021 at 21:42:55 UTC, Per Nordlöw wrote: On Wednesday, 6 January 2021 at 09:21:53 UTC, Mike Parker wrote: https://github.com/dlang/DIPs/blob/c06ce7f144b3dabf363d1896ddcd31a2a6b7c969/DIPs/DIP1039.md A bit off topic: Would Kenji Hara still have been an active Dlang community member if his solution to DIP-1039 hadn't been reverted. Please start a new thread for that and let's keep this one focused on this DIP. Thanks!
DIP 1039--Static Arrays with Inferred Length--Community Review Round 1 Begins
The first round of Community Review for DIP 1039, "Static Arrays with Inferred Length", is now under way. Please discuss the DIP (its merits, its implementation, peripheral topics, etc.) in the Discussion Thread and save all review feedback (critiques on the content of the DIP: what to change, how to improve it, etc.) for the Feedback Thread. Discussion Thread: https://forum.dlang.org/post/ucqyqkvaznbxkasvd...@forum.dlang.org Feedback Thread: https://forum.dlang.org/post/qglydztoqxhhcurvb...@forum.dlang.org
Discussion Thread: DIP 1039--Static Arrays with Inferred Length--Community Review Round 1
This is the discussion thread for the first round of Community Review of DIP 1039, "Static Arrays with Inferred Length": https://github.com/dlang/DIPs/blob/c06ce7f144b3dabf363d1896ddcd31a2a6b7c969/DIPs/DIP1039.md The review period will end at 11:59 PM ET on January 20, or when I make a post declaring it complete. Discussion in this thread may continue beyond that point. Here in the discussion thread, you are free to discuss anything and everything related to the DIP. Express your support or opposition, debate alternatives, argue the merits, etc. However, if you have any specific feedback on how to improve the proposal itself, then please post it in the feedback thread. The feedback thread will be the source for the review summary that I will write at the end of this review round. I will post a link to that thread immediately following this post. Just be sure to read and understand the Reviewer Guidelines before posting there: https://github.com/dlang/DIPs/blob/master/docs/guidelines-reviewers.md And my blog post on the difference between the Discussion and Feedback threads: https://dlang.org/blog/2020/01/26/dip-reviews-discussion-vs-feedback/ Please stay on topic here. I will delete posts that are completely off-topic.
Re: Discussion Thread: DIP 1039--Static Arrays with Inferred Length--Community Review Round 1
On Wednesday, 6 January 2021 at 09:21:53 UTC, Mike Parker wrote: However, if you have any specific feedback on how to improve the proposal itself, then please post it in the feedback thread. The feedback thread will be the source for the review summary that I will write at the end of this review round. I will post a link to that thread immediately following this post. The Feedback Thread is here: https://forum.dlang.org/post/qglydztoqxhhcurvb...@forum.dlang.org
DIP 1033--Implicit Conversion of Expressions to Delegates--Postponed
The Final Review of DIP 1033, "Implicit Conversion of Expressions to Delegates", wrapped up early this month. At the time, after a discussion about the DIP with Atila, Walter asked me to delay the Formal Assessment. More recently, he has informed me that he needs to give some thought as to how to move forward, but he currently has other pressing needs taking up his time (like his SIMD bug-fixing spree). So we have marked the DIP as Postponed until he is ready to come back to it. https://github.com/dlang/DIPs/blob/8320cbbeea8020eb33d59f05fc4e27f007e3544f/DIPs/other/DIP1033.md
Re: Our community seems to have grown, so many people are joining the Facebook group
On Tuesday, 29 December 2020 at 13:04:42 UTC, Tobias Pankrath wrote: You have a valid point, but still I am sure the facebook group is a net positive for the community. I'd see it as a digital version of a local user group. Yeah, I see no problem with the group existing. I think it's great. It will reach people who might otherwise not have heard of D, and it's an option for those who are used to using FB groups instead of forums/IRC/Discord/etc.
Re: Our community seems to have grown, so many people are joining the Facebook group
On Tuesday, 29 December 2020 at 00:38:40 UTC, Murilo wrote: And apart from all that, having an official FB group serves to show Dlang is growing strong and proud, it shows the world that Dlang is not dead(most people think it is). I'm happy it's working for you, but please do not present it as an "official" group. That implies the foundation is involved in operating it.
Re: BeerConf Mid-December Edition
On Sunday, 20 December 2020 at 11:39:14 UTC, Selim Ozel wrote: On Saturday, 19 December 2020 at 17:48:37 UTC, Ethan wrote: On Saturday, 19 December 2020 at 15:15:16 UTC, Iain Buclaw wrote: I've started up a meeting for people to come and go as they please. BEERCONF Did I miss this? That sucks! When's the next one and what is this "stream". Sorry if it's a totally n00b quesiton. Best, S It will be open all weekend. They usually run both Saturday and Sunday. If no one is there when you peek in, just keep the tab open or check again later. I believe the peak time is usually in the central European evening.
DIP 1038--@nodiscard--Community Review Round 1
The first round of Community Review for DIP 1038, "@nodiscard", is now under way. Please discuss the DIP (its merits, its implementation, peripheral topics, etc.) in the Discussion Thread and save all review feedback (critiques on the content of the DIP: what to change, how to improve it, etc.) for the Feedback Thread. Discussion Thread: https://forum.dlang.org/post/zlanrlqqjjtvfwbym...@forum.dlang.org Feedback Thread: https://forum.dlang.org/post/qptthjobogoooclei...@forum.dlang.org
Re: DConf Online Video & Slide Links
On Monday, 7 December 2020 at 10:29:24 UTC, Mike Parker wrote: After a brief respite, I've gotten back to work. I've just updated the DConf Online site with links to all the slides (including Mathis Beer's) and prerecorded videos. https://dconf.org/2020/online/index.html
DConf Online Video & Slide Links
After a brief respite, I've gotten back to work. I've just updated the DConf Online site with links to all the slides (including Mathis Beer's) and prerecorded videos. In the coming days, I'll add the slide links to the video descriptions on YouTube and chop up the Q & A livestreams into individual videos for a Q & A playlist. The full streams won't go anywhere, though.
Re: BeerConf Mid-December Edition
On Monday, 7 December 2020 at 08:35:35 UTC, Iain Buclaw wrote: So one more time for 2020, grab your best-loved beverages and revered D topics, and join us December 19-20th to celebrate all that we've collectively achieved this year, before finally banishing 2020 into history's dustbin (and sanitize it twice for good measure). Woohoo! I think I'll exchange the cider for actual beer this time.
Re: DConf Online 2020 was a big success!
On Wednesday, 25 November 2020 at 20:30:39 UTC, oddp wrote: On 25.11.20 21:00, Faux Amis via Digitalmars-d-announce wrote: Is there any way to watch the livestreams in stead of the presentations only? Well, the youtube channel has these two Q livestreams, each around six hours long, along with chat: Day 1: https://www.youtube.com/watch?v=o-2_mxaCL9w Day 2: https://www.youtube.com/watch?v=3XhsLUudelM You might want to watch them at 1.75x+ speed. :) I'm going to chop those up and post them as individual videos in a Q & A playlist. The full livestreams will remain, though, and I'll update the description with timestamps for each talk. I'll start on all of that next week.
Re: DConf Online 2020 was a big success!
On Monday, 23 November 2020 at 07:39:58 UTC, Walter Bright wrote: Thanks go out to all the people who helped out by asking questions that made the chats interesting and informative. Special thanks go out to our speakers who provided the technical presentations: Seconded. The presentations turned out great and I was happy to see the participation in the chats. And I'm glad the livestream was livelier than I had expected or intended it to be -- it was more fun that way. And Extra Special Double-Secret Thanks to Mike Parker, who: Thanks, Walter! I learned a lot on this first outing that we can apply to the next one a year from now.
How to Participate in DConf Online 2020
I've written up a blog post describing how to take part in DConf Online 2020. If anything isn't clear, let me know. https://dlang.org/blog/2020/11/20/dconf-online-2020-how-to-participate/
One More DConf Online 2020 Schedule Adjustment
In the course of scheduling the video premieres on our YouTube channel, I learned that YouTube only offers time options on the hour and every quarter hour after. Since a few of the talks were listed on the website schedule as starting at :10, :20, or :40, I've had to adjust them 5-minutes back or ahead. The affected talks are: Nov 21 Alexandru Militaru: from 17:20 UTC to 17:15 Mathias Lang: from 19:10 UTC to 19:15 Nov 22 Mathis Beer: from 15:20 UTC to 15:15 Ali Çehreli: from 16:40 UTC to 16:45 Stefan Koch: from 19:20 UTC to 19:15 I've got a blog post coming shortly describing how to participate, with all the necessary links.
DIP 1033--Implicit Conversion of Expressions to Delegates--Final Review Begins
The Final Review for DIP 1033, "Implicit Conversion of Expressions to Delegates", 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 when no revisions were made, it's a final opportunity to catch any problems that may have been missed before. Please discuss the features of the proposal (its merits, its implementation, peripheral topics, etc.) in the Discussion Thread and save all review feedback (critiques on the content of the DIP: what to change, how to improve it, etc.) for the Feedback Thread. Discussion Thread: https://forum.dlang.org/post/ysdmdeemnrfwqemkj...@forum.dlang.org Feedback Thread: https://forum.dlang.org/post/tvwikrkcqqyeyprfd...@forum.dlang.org
Re: Another DConf Online 2020 Schedule Change
On Monday, 16 November 2020 at 06:27:48 UTC, Mike Parker wrote: moved from 19:20 UTC on Sunday to 15:20 UTC on Saturday. Sorry, that should be 17:20 UTC on Saturday.
Another DConf Online 2020 Schedule Change
Now that we know exactly how long the talks are, we found the need to fill some dead space for a video shorter than expected and reclaim some extra post-talk Q & A space for a video that turned out longer than expected. So we shuffled the schedule around a bit to make it happen. The biggest change is that Alexandru Militaru's talk has been moved from 19:20 UTC on Sunday to 15:20 UTC on Saturday. Other than that, the start of Ali and Robert's talks on Saturday have been moved to slightly earlier times (14:45 UTC and 16:00 UTC, respectively), and Stefan's talk on Sunday is back in its original 19:20 UTC slot. https://dconf.org/2020/online/index.html#schedule
Preparing for Google Summer of Code 2021
Recently, Google put out an announcement on the GSoC mailing list about their plans for GSoC 2021. They're doing things differently this time. A big change is that the event is being cut down to 10 weeks, with 2 evaluations rather than 3. That means we will need to think of project ideas that fit into a shorter time period than in the past. Everyone, please start thinking of suitable projects and submitting your ideas to the dlang/projects repository: https://github.com/dlang/projects Mentor stipends on the new schedule are set at $400, so it's not much less than before. We encourage those of you with solid D experience, or domain experience related to any of the potential projects in the repository above, to put yourself forward as a potential mentor. They're also relaxing the eligibility requirements to allow participation from a broader range of applicants: "In 2020 there are many ways students are learning and we want to acknowledge that so we will be allowing students who are 18 years old AND currently enrolled (or accepted into) a post-secondary academic program as of May 17, 2021 or have graduated from a post-secondary academic program between December 1, 2020 and May 17, 2021 to apply to the GSoC program. What this means is that now the program will be open to folks participating in a variety of different academic programs, not just accredited university programs. This includes licensed coding camps, community colleges, and many other programs that may not be accredited yet but are post-secondary academic programs."
Re: DConf Online 2020 Schedule Change
On Thursday, 12 November 2020 at 17:01:51 UTC, Greatsam4sure wrote: On Thursday, 12 November 2020 at 08:34:46 UTC, Mike Parker wrote: On Wednesday, 11 November 2020 at 12:33:44 UTC, Greatsam4sure wrote: Is Andrei not having anything for the community in this dlang online conference? All the talks are in the published schedule. I have checked the list of people giving talks but I did not found Andrei's name, that is why I am asking. That means the answer to your question is no.
Re: DConf Online 2020 Schedule Change
On Wednesday, 11 November 2020 at 12:33:44 UTC, Greatsam4sure wrote: Is Andrei not having anything for the community in this dlang online conference? All the talks are in the published schedule.
DConf Online 2020 Schedule Change
On the first day of the conference, we've swapped Robert and Ali's timeslots. Ali's talk is now at 15:20 UTC and Robert's is at 16:40. https://dconf.org/2020/online/index.html
Re: New DConf Online 2020 Lightning Talk and a new Task Bounty
On Monday, 2 November 2020 at 18:23:35 UTC, Seb wrote: I'm sorry about the rather aggressive tone. Thank you.
Re: New DConf Online 2020 Lightning Talk and a new Task Bounty
On Monday, 2 November 2020 at 15:08:43 UTC, Seb wrote: A worrying side note here is that there have been many private and public mails about the root causes (three years ago the registry was crashing because the VM only had 200M of memory and a small GC leak made the server collect slightly more memory than it should). Anyhow, even without prior knowledge an email to anyone who has ever contributed code to the registry - aka its maintainers - (e.g. Sönke, Martin, WebFreak, ZombineDev, Mathias, ...) would have yielded this information - very similar to the recent LDC bounty that was done without contacting any of the LDC maintainers. First of all, this is nothing like the LDC situation. That was something I absolutely should have contacted someone about, and when I was made aware of my mistake I apologized for it. My inbox is a graveyard of unanswered emails. I can't count off the top of my head the things that have been delayed or that have never happened because of that. So in the interest of getting things done, when someone wants to put a bounty on an open issue, if I judge it to be a simple contribution (i.e., something that isn't dependent on existing work, or doesn't require special consideration/permission, etc) then I'm not going to email anyone about it. The very first step on this bounty is to summarize the commits for a changelog. I don't need to contact anyone for that. The last step is to ensure that a release tag is made. That means anyone pursuing the bounty would have to contact one of the maintainers at some point. Again, it's a simple contribution, so I treated it as I would any other open issue. My mistake was assuming that because it's an open issue, it still hasn't been resolved. Had I checked the release tags and the dates, I would have seen that a release has since been made. But I didn't, so mea culpa. However, our conversation could have gone like this: You: Hey, Mike, I pushed out a release in September: https://github.com/dlang/dub-registry/releases/tag/v2.4.0 Me: Oh, okay, I'll see what else he wants to put the money toward. Thanks! So yes, I will close the bounty and ask the donor where he wants me to direct the cash.
New DConf Online 2020 Lightning Talk and a new Task Bounty
We've added a "lightning talk" to the DConf Online 2020 schedule. Alexandru Militaru, whom you may remember from his DConf 2019 presentation, will give a ~15-minute talk about sil-cling, an extension to the Symmetry Integration Language (SIL). The talk is taking the 19:20 UTC slot on November 22, and Stefan Koch's talk has been moved to 19:50. https://dconf.org/2020/online/index.html#schedule DConf 2019 talk: http://dconf.org/2019/talks/militaru.html An anonymous donor has seeded a new Task Bounty with $400. The task: execute a new release of the dub-registry project. https://www.flipcause.com/secure/cause_pdetails/MTAwNzkx The same donor bumped up the bounty for the task to improve DLL support on Windows. It's now up to $320. https://www.flipcause.com/secure/cause_pdetails/ODcyMDE=
bindbc-sfml 0.1.0
I've finally gotten around to finishing up the port of DerelictSFML2 to BindBC: http://bindbc-sfml.dub.pm/ Unlike the Derelict package, it supports every release of CSFML from 2.0 to 2.5. It's untested beyond compiling and loading, so I appreciate any bug reports anyone files. One issue I encountered myself is this one when loading the CSFML Network library: https://github.com/BindBC/bindbc-sfml/issues/1 It's got me stumped, but I have no more time to put toward it at the moment. For those not in the know, SFML is a C++ library designed for game and multimedia development. CSFML is the set of official C bindings. https://www.sfml-dev.org/ https://www.sfml-dev.org/download/csfml/
Re: DConf Online 2020 Schedule
On Tuesday, 27 October 2020 at 12:16:00 UTC, IGotD- wrote: On Wednesday, 14 October 2020 at 12:41:34 UTC, Mike Parker wrote: The DConf Online schedule is now live on the website. I've got a blog post coming tomorrow which will, among other things, include an announcement about the schedule aimed at the world outside our community in a form suitable for /r/programming. https://dconf.org/2020/online/index.html Were the seminars recorded so that we can view them later? The talks are prerecorded. But even the livestreams will still be available on our YouTube channel afterwards.
DIP 1037--Add Unary Operator ...--Community Review Round 1 Begins
The first round of Community Review for DIP 1037, "Add Unary Operator ...", is now under way. Please discuss the DIP (its merits, its implementation, peripheral topics, etc.) in the Discussion Thread and save all review feedback (critiques on the content of the DIP: what to change, how to improve it, etc.) for the Feedback Thread. Discussion Thread: https://forum.dlang.org/post/alsfzarhhszauufbx...@forum.dlang.org Feedback Thread: https://forum.dlang.org/post/rihufokcywwlityfl...@forum.dlang.org
Re: DConf Online 2020 Schedule
On Wednesday, 14 October 2020 at 12:41:34 UTC, Mike Parker wrote: I've got a blog post coming tomorrow The blog: https://dlang.org/blog/2020/10/15/d-2-094-0-dconf-online-schedule-and-saoc-2020/ Reddit: https://www.reddit.com/r/programming/comments/jbp7j6/d_2094_released/
Re: DConf Online 2020 Schedule
On Wednesday, 14 October 2020 at 14:07:39 UTC, Ezneh wrote: I found few typos in the following parts of the text: Thanks!
DConf Online 2020 Schedule
The DConf Online schedule is now live on the website. I've got a blog post coming tomorrow which will, among other things, include an announcement about the schedule aimed at the world outside our community in a form suitable for /r/programming. https://dconf.org/2020/online/index.html
Re: DConf Online 2020...
On Saturday, 3 October 2020 at 23:37:37 UTC, Mike Parker wrote: On Saturday, 3 October 2020 at 23:15:41 UTC, Ali Çehreli wrote: On 10/3/20 4:12 PM, Walter Bright wrote: What's the hashtag? #dconf2020 ? Me not know hashtag but Mike has been saying that this is not a DConf but a "DConf Online". Two different yearly events... :) Ali #dconf2020 works. I thought the question was regarding the forums. For twitter, I've always just used #dconf.
Re: DConf Online 2020...
On Saturday, 3 October 2020 at 23:15:41 UTC, Ali Çehreli wrote: On 10/3/20 4:12 PM, Walter Bright wrote: What's the hashtag? #dconf2020 ? Me not know hashtag but Mike has been saying that this is not a DConf but a "DConf Online". Two different yearly events... :) Ali #dconf2020 works.
Re: DConf Online 2020...
On Saturday, 3 October 2020 at 04:31:35 UTC, Dukc wrote: Did you remember the schelude publication? It was supposed to happen yesterday. Yes. I'm behind schedule, but it's coming soon.
Function Generation in D: The Good, the Bad, the Ugly, and the Bolt
Jean-Louis Leroy sent in a blog post prompted by Andrei's "Perfect forwarding" challenge from the July #beerconf. He digs into D's metaprogramming and code generation facilities, and shows how he arrived at his "refraction" module. The blog: https://dlang.org/blog/2020/09/28/function-generation-in-d-the-good-the-bad-the-ugly-and-the-bolt/ Reddit: https://www.reddit.com/r/programming/comments/j1c6l6/function_generation_in_d_the_good_the_bad_the/
DIP 1034--Add a Bottom Type (reboot)--Final Review Begins
The Final Review for DIP 1034, "Add a Bottom Type (reboot)", 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 when no revisions were made, it's a final opportunity to catch any problems that may have been missed before. Please discuss the features of the proposal (its merits, its implementation, peripheral topics, etc.) in the Discussion Thread and save all review feedback (critiques on the content of the DIP: what to change, how to improve it, etc.) for the Feedback Thread. Discussion Thread: https://forum.dlang.org/post/heylgwkzcpfqmqyti...@forum.dlang.org Feedback Thread: https://forum.dlang.org/post/ceicwtqcalmgiteud...@forum.dlang.org
Re: DIP 1030-- Named Arguments--Formal Assessment
On Friday, 18 September 2020 at 13:34:30 UTC, Jean-Louis Leroy wrote: On Thursday, 17 September 2020 at 12:58:06 UTC, Mike Parker wrote: So they decided that a new `std.traits` template and a corresponding `__traits` option are needed which expand into the exact function signature of another function. I have been trying to locate that specific discussion, without success so far. Help? This is of great interest to me, and I may throw in my $.02. It's from a phone call they had while they were discussing whether to approve or reject the DIP.
Re: What Mike thinks
On Thursday, 17 September 2020 at 20:13:23 UTC, Cym13 wrote: On Thursday, 17 September 2020 at 13:45:16 UTC, Mike Parker wrote: What Mike thinks appears nowhere in my post :-) That's a bit sad. I understand that in your position it may be hard to express a personnal opinion but I think anyone should get the opportunity to do so. Would you like, in no official capacity whatsoever, to provide your personnal take on the matter? I think you took that comment the wrong way :-) The announcement provides the rationale behind the decision Walter and Atila made. I just wanted to make it clear for anyone reading Jean-Louis's comment that I wasn't posting my opinion. For the record, I have no opinion on this DIP one way or another. Named arguments don't interest me at all. I think you should get to express your feelings as well :) But of course I would understand if you don't want to get involved in any particular issue. Given that I work closely with DIP authors to revise their DIPs, and that sometimes that involves more than just proofreading, I don't think it's appropriate for me to publicly take a position on any of them. I don't want any author to feel I have an ulterior motive in any content revision suggestions I make, and I don't want to color my own judgement.
Re: DIP 1030-- Named Arguments--Formal Assessment
On Thursday, 17 September 2020 at 13:42:47 UTC, Jean-Louis Leroy wrote: this point I have some hope that the DIP is not damaging in the way Mike thinks. What Mike thinks appears nowhere in my post :-)
DIP 1030-- Named Arguments--Formal Assessment
DIP 1030, "Named Arguments", has been accepted.
During the assessment, Walter and Atila had a discussion
regarding this particular criticism:
https://forum.dlang.org/post/mailman.1117.1581368593.31109.digitalmar...@puremagic.com
"Named arguments breaks this very important pattern:
auto wrapper(alias origFun)(Parameters!origFun args)
{
// special sauce
return origFun(args);
}"
They say that, though it's true that `Parameters!func` will not
work in a wrapper, it "doesn't really work now"---default
arguments and storage classes must be accounted for. This can be
done with string mixins, or using a technique referred to by
Jean-Louis Leroy as "refraction", both of which are clumsy.
So they decided that a new `std.traits` template and a
corresponding `__traits` option are needed which expand into the
exact function signature of another function.
They also acknowledge that when an API's parameter names change,
code depending on the old parameter names will break. Struct
literals have the same problem and no one complains (the same is
true for C99). And in any case, when such a change occurs, it's a
hard failure as any code using named arguments with the old
parameter names will fail to compile, making it easy to see how
to resolve the issue. Given this, they find the benefits of the
feature outweigh the potential for such breakage.
Re: DIP 1030-- Named Arguments--Formal Assessment
On Thursday, 17 September 2020 at 12:58:06 UTC, Mike Parker wrote: DIP 1030, "Named Arguments", has been accepted. https://github.com/dlang/DIPs/blob/master/DIPs/accepted/DIP1030.md
Re: DConf Online 2020...
On Wednesday, 9 September 2020 at 13:10:39 UTC, James Lu wrote: On Tuesday, 8 September 2020 at 09:17:10 UTC, Mike Parker wrote: I was on the verge to cutting the schedule down to one day, but thanks to some last-minute submissions, looks like we'll have enough content now to stretch across two days! Thanks to everyone who submitted a proposal. I'll be in touch with each of you soon to discuss how to proceed. For everyone else, keep an eye on the DConf Online 2020 homepage for the schedule and other announcements. https://dconf.org/2020/online/index.html Would you accept extra-late proposals? Yes, with the understanding that priority goes to those who met the deadline. If I don't use it for the conference, I still need content with which to seed our new YouTube playlist.
Re: DConf Online 2020...
On Wednesday, 9 September 2020 at 07:52:53 UTC, FeepingCreature wrote: On Tuesday, 8 September 2020 at 09:17:10 UTC, Mike Parker wrote: I was on the verge to cutting the schedule down to one day, but thanks to some last-minute submissions, looks like we'll have enough content now to stretch across two days! Yay! How close was it? Half the submissions in the last six hours? A couple during the extended week, a couple at the deadline, and a couple of people who had offered to do something if there weren't enough submissions.
DIP 1036--Formatted String Tuple Literals--Community Review Round 1 Begins
The first round of Community Review for DIP 1036, "Formatted String Tuple Literals", is now under way. Please discuss the DIP (its merits, its implementation, peripheral topics, etc.) in the Discussion Thread and save all review feedback (critiques on the content of the DIP: what to change, how to improve it, etc.) for the Feedback Thread. Discussion Thread: https://forum.dlang.org/post/vwrbvacnuerasbphg...@forum.dlang.org Feedback Thread: https://forum.dlang.org/post/vpgemqdqgorsuzqbx...@forum.dlang.org
DConf Online 2020...
I was on the verge to cutting the schedule down to one day, but thanks to some last-minute submissions, looks like we'll have enough content now to stretch across two days! Thanks to everyone who submitted a proposal. I'll be in touch with each of you soon to discuss how to proceed. For everyone else, keep an eye on the DConf Online 2020 homepage for the schedule and other announcements. https://dconf.org/2020/online/index.html Also, please don't forget, we could use your support! Help us out by purchasing some DConf 2020 swag from our online store: https://www.zazzle.com/store/dlang_swag?rf=238129799288374326 We receive a commission on all the produces listed there. Plus, anything you by via the above link, whether it's our swag or something else, will send a little more our way in referral fees. All the proceeds go into our General Fund. You can also help out by donating directly to the General Fund: https://www.flipcause.com/secure/cause_pdetails/NDMzMzE= We'll be pulling a little from the General Fund to provide DConf Online 2020 t-shirts and coffee mugs to our speakers and prizes to random participants during the conference.
Re: DConf Online 2020 Submission Deadline Extended
On Sunday, 6 September 2020 at 13:29:55 UTC, Darren Drapkin wrote: On Monday, 31 August 2020 at 08:36:09 UTC, Mike Parker wrote So send me your <= 5-minute videos describing your talks, folks! What do you think ? -- Seems interesting! But the purpose of requiring video submissions is to make sure that everyone who submits a talk is set up to record it. We need to get an idea not only of the content, but that you are set up for screencasting (for the slides) and that there are no obvious issues with your basic setup. We want to catch any of those (such as poor audio quality) before you sit down and put together a full talk. So please submit this as a video. No need for a camera even. A screencast with your voice is fine.
Re: DConf Online 2020 Submission Deadline Extended
On Monday, 31 August 2020 at 08:36:09 UTC, Mike Parker wrote: I've received exactly one submission for DConf Online. Two keynotes + one talk does not make a conference. So this is the last call. The deadline has been extended to Sunday, September 6 AOE. This makes or breaks the conference. If we don't have enough talks submitted, it ain't happening. I've gotten one more submission. We'll need more than that. Let's go, folks!
DConf Online 2020 Submission Deadline Extended
I've received exactly one submission for DConf Online. Two keynotes + one talk does not make a conference. So this is the last call. The deadline has been extended to Sunday, September 6 AOE. This makes or breaks the conference. If we don't have enough talks submitted, it ain't happening. So send me your <= 5-minute videos describing your talks, folks! https://dconf.org/2020/online/index.html
Symmetry Investments and the D Language Foundation are Hiring
Looking for a full-time or part-time gig? Not only is Symmetry Investments hiring D programmers, they are also generously funding two positions for ecosystem work under the D Language Foundation. And they've put up a bounty for a new DUB feature. Read all about it here: https://dlang.org/blog/2020/08/30/symmetry-investments-and-the-d-language-foundation-are-hiring/
Re: Where are the DConf Online Submissions?
On Sunday, 30 August 2020 at 00:13:19 UTC, Stefan Koch wrote: https://dconf.org/2020/online/index.html You don't need to do the whole talk on the video submission right? Right. A short video, no more than 5-minutes. Details are on the site.
Where are the DConf Online Submissions?
In my experience with DConf and SAOC, a number of submissions/applications come in on the last day, but I usually receive a some before then. So far, I haven't seen a single submission for DConf Online. If need be, I will extend the deadline by a week. I've been hoping to have enough submissions for at least six videos per day, including the keynotes from Walter and Atila. Anything less than that isn't going to be much of a conference. So if you guys want to see DConf Online happen, then you need to send me some video submissions! https://dconf.org/2020/online/index.html
Re: The ABC's of Templates in D
On Saturday, 29 August 2020 at 09:18:56 UTC, Robert M. Münch wrote: A bit late... but I don't understand this part: "Unlike x, p is not a member of the template. The type Pair is a member, so we can’t refer to it without the prefix." * Why is it not a member of the template (specification)? The variable p is declared outside of the template. The type of p is a template member, it's declared inside the template, but p itself is not. * Later it is a member... of what if not of the template (specification)? I don't understand what you mean. p is not a member of anything. Confusing...
DIP 1032--Function Pointer and Delegate Parameters--Withdrawn
At the end of the final review of DIP 1032, "Function Pointer and Delegate Parameters Inherit Attributes from Function", Walter informed me he had decided he would reject the DIP on the grounds that it doesn't offer enough utility to justify the potential for code breakage. Since the DIP was not yet in the Formal Assessment stage, and there's no need to keep it around in the Post-Final queue, I've marked it as 'Withdrawn' and it has now been relegated to the graveyard of the 'DIPS/other' directory. https://github.com/dlang/DIPs/blob/master/DIPs/other/DIP1032.md
SAOC 2020 Projects and Participants
If you're interested in following along with the progress of Symmetry Autumn of Code 2020, you can start with this blog post, where I briefly introduce the participants and their SAOC projects: https://dlang.org/blog/2020/08/23/symmetry-autumn-of-code-2020-projects-and-participants/
SAOC 2020 Phase One
We've passed the SAOC 2020 application deadline and have received a handful of applications. The SAOC committee will evaluate them over the coming days. I'll announce the participants and their projects next Sunday, August 23 with and introduction the participants and their projects on the blog. Thanks to everyone who submitted an application. And special thanks to Razvan and Edi for the good work they're doing in stoking interest in D!
