Re: Phobos now compiling with -dip1000
On Sat, Mar 23, 2019 at 12:01:49AM -0400, Nick Sabalausky (Abscissa) via Digitalmars-d-announce wrote: > On 3/22/19 11:06 PM, Walter Bright wrote: > > Many thanks to Sebastian Wilzbach, Nicholas Wilson, Mike Franklin, > > and others! > > > > It's been a long and often frustrating endeavor, but we made it and > > I'm very pleased with the results. [...] > Ie DIP1000: "Scoped Pointers": "...provides a mechanism to guarantee > that a reference cannot escape lexical scope" in large part to aid > non-GC memory management. > > With that aside, this does indeed sound like a great milestone (not > that I doubted!). Kudos and congrats all around! Does that mean -dip1000 will become the default compiler behaviour in the near future? Also, does it only apply to @safe code, so that I have to start annotating stuff with @safe in order to benefit from it? T -- Meat: euphemism for dead animal. -- Flora
Re: Phobos now compiling with -dip1000
On 3/22/19 11:06 PM, Walter Bright wrote: Many thanks to Sebastian Wilzbach, Nicholas Wilson, Mike Franklin, and others! It's been a long and often frustrating endeavor, but we made it and I'm very pleased with the results. At the risk of embarrassing myself: Am I the only one who finds they need to google a DIP number every single time in order to have any idea what it refers to? (And then massage the query to get to the right place.) On the off chance I'm not alone: https://github.com/dlang/DIPs/blob/master/DIPs/other/DIP1000.md Ie DIP1000: "Scoped Pointers": "...provides a mechanism to guarantee that a reference cannot escape lexical scope" in large part to aid non-GC memory management. With that aside, this does indeed sound like a great milestone (not that I doubted!). Kudos and congrats all around!
Phobos now compiling with -dip1000
Many thanks to Sebastian Wilzbach, Nicholas Wilson, Mike Franklin, and others! It's been a long and often frustrating endeavor, but we made it and I'm very pleased with the results.
Re: New DConf Blog Post
On 3/22/19 9:58 AM, Mike Parker wrote: The DConf schedule was announced last Sunday. I've just published a write-up about it on the blog for the world-at-large. Please help us out by sharing this post in your social media circles. The blog: https://dlang.org/blog/2019/03/22/dconf-2019-london-programme/ Reddit: https://www.reddit.com/r/programming/comments/b45bxp/dconf_2019_london_programme/ Side note, I started using mewe (and I really am not a social media type, so I doubt it will get a lot of use from me). And I created a Dlang group, if anyone is on there, feel free to join. https://mewe.com/group/5c7174c35ff915267872a688 -Steve
New DConf Blog Post
The DConf schedule was announced last Sunday. I've just published a write-up about it on the blog for the world-at-large. Please help us out by sharing this post in your social media circles. The blog: https://dlang.org/blog/2019/03/22/dconf-2019-london-programme/ Reddit: https://www.reddit.com/r/programming/comments/b45bxp/dconf_2019_london_programme/
Re: GtkD Blog Post #0005 Now Live
On Thursday, 21 March 2019 at 13:22:49 UTC, number wrote: Thank you for these tutorials! Again, thanks for reading, number. And to anyone else also reading: Please drop a line here or on Mike Wey's https://forum.gtkd.org to let me know you're following along. I've been so busy working on code examples and blog posts, as well as doing all that life stuff, I haven't had time to set up an engagement statistics app on the blog site. (To be frank, web technology has raced ahead of me over the last ten years and I'm still playing catch up).
Re: GtkD Blog Post #0005 Now Live
On Thursday, 21 March 2019 at 13:22:49 UTC, number wrote:
On Tuesday, 29 January 2019 at 21:00:10 UTC, Ron Tarrant wrote:
Another blog post available at http://gtkdcoding.com
Enjoy!
Thank you for these tutorials!
Just want to mention that the code on the page (0005) is not in
sync with the one on github. In the else branch, the former
uses 'window.setSizeRequest(640, 480)' where the latter uses
'window.setSizeRequest(-1, -1);' and the comment doesn't make
sense with the use of -1 because the limit is actually removed.
As for the first code ('Pre-Size a Window'): setSizeRequest()
might be 'simple' but that doesn't explain what it does, i.e.
setting a minimum size.
You're right. I noticed as I was getting my Linux installation
working that this particular example behaves differently
depending on whether it's compiled on Windows or Linux. I had
planned to go back and take another look to figure out what those
differences were, but just haven't gotten to it yet.
I'll get at it as soon as time allows. In the meantime, I hope it
doesn't distract too much.
Thanks for bringing this back into the forefront for me.
Re: gtkDcoding Blog Post #0007 Now Live
On Thursday, 21 March 2019 at 15:59:29 UTC, number wrote: The 0007 github code doesn't compile. button_002_05_release.d(40): Error: undefined identifier buttonCaption buttonCaption is now defined (and unused) in the button class but still used in the window class and the button constructor still uses the label argument. I forgot to say, these have all been corrected.
Re: gtkDcoding Blog Post #0007 Now Live
On Thursday, 21 March 2019 at 15:59:29 UTC, number wrote: The 0007 github code doesn't compile. button_002_05_release.d(40): Error: undefined identifier buttonCaption buttonCaption is now defined (and unused) in the button class but still used in the window class and the button constructor still uses the label argument. Wow! I thought I was being sooo careful. Thank you once again for catching all these errors, mistakes, typos, and outright faux pas.
