Re: Release D 2.101.0
On Tuesday, 15 November 2022 at 20:54:03 UTC, Iain Buclaw wrote: a new `std.typecons.SafeRefCounted` type that can be used in `@safe` Nice! Thank you, dukc. Excited to see dirEntries finally be @safe with dip1000. God speed to the ones who figuring out the @safe inference issue with borrow.
Re: mysql-native v3.2.0 - the safe update
On Saturday, 23 April 2022 at 05:12:30 UTC, Steven Schveighoffer wrote: It's happened. I opened the PR over 2 years ago, and just got around to bringing it up to date in the last few days. This is a huge huge update. I've never done anything like this before, but I think it works as a drop-in replacement, while allowing you to migrate any piece you wish from unsafe code to safe code. Please let me know if there are *any* problems you find with this. See the [safe migration doc](https://github.com/mysql-d/mysql-native/blob/master/SAFE_MIGRATION.md) for more details. Note this does *not* build with dip1000, because the two underlying libraries (Phobos sockets and vibe.d) do not build as safe with dip1000. -Steve Awesome, thank you!
Re: mysql-native release 3.1.0
Thanks for the release. You guys are awesome!
Re: Why I Like D
On Wednesday, 12 January 2022 at 02:37:47 UTC, Walter Bright wrote: "Why I like D" is on the front page of HackerNews at the moment at number 11. https://news.ycombinator.com/news Nice article, especially this paragraph: In case you are writing a performance critical piece of software, remember you can turn off the garbage collector! People on forums like to bash that in such case you cannot use many functions from standard library. So what? If performances are essential for your system you are likely already writing you own utility library with highly optimized algorithms and data structures for your use case, so you won’t really miss the standard library much. Good luck to the boys and girls in the HN comments as the dumpster fire is already raging.
Re: He Wrote a High-Frequency Trading Platform in D
On Saturday, 11 December 2021 at 13:58:02 UTC, Mike Parker wrote: Georges Toutoungis shared his D user experience on the D blog. He went from being excited, to dismissive, to using D to implement an HFT and never looking back. The blog: https://dlang.org/blog/2021/12/11/i-wrote-a-high-frequency-trading-platform-in-d/ Reddit: https://www.reddit.com/r/programming/comments/re075b/he_wrote_a_highfrequency_trading_platform_in_d/ This is cool! However, the reddit comments are a trash fire as usual, and I hope most people skip them after reading the article, directly trying D instead.
Re: Beta 2.098.0
On Sunday, 10 October 2021 at 23:36:56 UTC, surlymoor wrote: Meanwhile @live is in the language, and it's half-baked. Then there's preview switches that will linger on into perpetuity; DIPs' implementations that haven't been finished. In retrospect, this is a rather crude message, especially from someone who doesn't contribute anything. Apologies.
Re: Beta 2.098.0
On Monday, 11 October 2021 at 00:34:28 UTC, Mike Parker wrote: On Sunday, 10 October 2021 at 23:36:56 UTC, surlymoor wrote: Meanwhile @live is in the language, and it's half-baked. Then there's preview switches that will linger on into perpetuity; DIPs' implementations that haven't been finished. And Walter has prioritized this issue over those. No matter what he works on, people will moan that he isn’t working on something else. Maybe we should clone him. My cousin has a vat filled with neon green liquid. Just let me know.
Re: Beta 2.098.0
On Sunday, 10 October 2021 at 23:11:56 UTC, Walter Bright wrote: ImportC resolves a long standing serious issue where multiple other substantial attempts at solving it have fallen short over the years. Unfortunately, ImportC is useless if it only half works. It has to work with existing C headers, which is why I'm concentrating on it to get to that point. Lack of ImportC has wasted a *lot* of developer time, making it a high leverage investment of time. [...] Meanwhile @live is in the language, and it's half-baked. Then there's preview switches that will linger on into perpetuity; DIPs' implementations that haven't been finished.
Re: mysql-native release v3.0.3
On Wednesday, 15 September 2021 at 13:42:39 UTC, Steven Schveighoffer wrote: Maybe you could take a look at how Mathias Lang does it [here](https://forum.dlang.org/post/zolkicvjrfkeoldkw...@forum.dlang.org) and see if it's easy to do something similar for mysql-native. I really would appreciate any help on getting the docs building! I know the previous versions used ddox (and a custom build of it at that), but I am not locked into that at all, and am willing for ANY documentation that is functional to replace it. It's critical to me that this is automatic, as I've published docs manually for other projects, I notice the result is, it doesn't get done. -Steve I tested a setup out, and it seemingly works. Will make a PR during night's reign.
Re: mysql-native release v3.0.3
On Tuesday, 14 September 2021 at 12:00:45 UTC, Steven Schveighoffer wrote: No worries, I am carving out time here and there to work on it. There are 2 heavy lifts here, both of which I think need to be done before a release. [...] Appreciate the information, and love that you're focused on the documentation aspect. Wish I or somebody else could help with that latter item at least, but I'm pretty useless. Regardless, hope all goes well.
Re: mysql-native release v3.0.3
On Tuesday, 14 September 2021 at 06:14:44 UTC, bauss wrote: See: https://github.com/mysql-d/mysql-native/pull/214#issuecomment-874692651 Thanks! Should've checked for recent activity before posting, it seems. Last I knew, Steven said there was some heavy-lifting to be done before merging, so I hope it hasn't been too burdensome.
Re: mysql-native release v3.0.3
On Saturday, 11 September 2021 at 16:38:28 UTC, Steven Schveighoffer wrote: I just tagged a new release. This fixes a couple of minor issues. See the [Changelog](https://github.com/mysql-d/mysql-native/blob/master/CHANGELOG.md) for details. -Steve Hey Steve, thank you for the work you're putting into this. Is there anything that needs to be done to expedite the @safe update's arrival, or is it just a lack of time?
Re: [Semi-OT] Sdlang Initiative
On Thursday, 9 September 2021 at 01:20:24 UTC, James Blachly wrote: I have finally come around to TOML as the best alternative for human-centered configuration. It seems to be really popular in Rust ecosystem. I see 3 D libraries; haven't tested them but will with my next D project: https://code.dlang.org/search?q=toml I was using `toml-foolery` for one of my projects. It's quite nice; however, there might be too many dependencies for some people, and a `RangeError` will be thrown up to you during parsing if there's an empty string for a key's value. While the latter is probably easy to remedy, I switched to using JSON since `asdf` was already a dependency, and I'm lazy. Still, a big thanks to Andrej for the work.
Re: mysql-native release v3.0.2
On Saturday, 29 May 2021 at 02:34:51 UTC, Steven Schveighoffer wrote: [...] Thanks for the work you, singingbush, et al., are putting into this project. Besides the glorious @safe update, any thoughts on supporting TLS connections? (Ideally, one's path to the DB wouldn't be routed outside of a protected network, but such is life.)
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: OK, I'm just concerned people will see the pattern: ```d somecfunc(str.toStringz); ``` and think that's the end of it. -Steve Pretty sure its documentation has a conspicuous warning regarding that.
