Re: D's Newfangled Name Mangling
On Wednesday, 20 December 2017 at 19:16:03 UTC, Ali Çehreli wrote: On 12/20/2017 07:41 AM, David Gileadi wrote: Typo: "This is were I stepped in..." -> "..where.." Yeah, an excellent post. Strangely, I could find just one typo myself. :) Its rather simple -> It's rather simple Thanks, guys!
Re: Silicon Valley D Meetup - December 14, 2017 - "Experimenting with Link Time Optimization" by Jon Degenhardt
On Saturday, 16 December 2017 at 11:52:37 UTC, Johan Engelen wrote: Clearly very interested in what your PGO testing will show. :-) Early returns on adding PGO on top of LTO (first five benchmarks in the slide deck, tsv-join not tested): * Two meaningful improvements: - csv2tsv: Linux: 8%; macOS: 33% - tsv-summarize: Linux: 6%; macOS: 11% * Minor improvements on the other three benchmarks (< 5%) Overall, for LDC 1.5, the improvements going from a normal optimized build to one combining LTO and PGO ranged from on 8-45% Linux, and 6-57% on macOS. (First five benchmarks, excluding tsv-join). Impressive! --Jon
Re: D's Newfangled Name Mangling
On 12/20/2017 07:41 AM, David Gileadi wrote: On 12/20/17 6:57 AM, Mike Parker wrote: Many thanks to Rainer for his insightful new article for the D Blog outlining the new name mangling algorithm. He talks about the old implementation and its limitations before going into the details of the new one. It's a topic I had never considered digging into before, even when the big Voldemort issue first popped up, but now I find it interesting. The blog https://dlang.org/blog/2017/12/20/ds-newfangled-name-mangling/ Reddit https://www.reddit.com/r/programming/comments/7l1h36/ds_newfangled_name_mangling/ I really enjoyed this! Typo: "This is were I stepped in..." -> "..where.." Yeah, an excellent post. Strangely, I could find just one typo myself. :) Its rather simple -> It's rather simple Ali
Re: D's Newfangled Name Mangling
On Wednesday, 20 December 2017 at 13:57:20 UTC, Mike Parker wrote: Many thanks to Rainer for his insightful new article for the D Blog outlining the new name mangling algorithm. Nice! "D and C++ avoid this problem by adding more information to the symbol name, i.e. they encode into a symbol name the scope in which the symbol is defined, the function argument types, and the return type. " I would change it to "... and the return type (D only)". C++ does not include the return type in the mangle for normal functions (it does for templates). An important difference, concerning the earlier remark about programs crashing when "fail to update and recompile all source files that use the new declarartion" -Johan
Re: D's Newfangled Name Mangling
On 12/20/17 6:57 AM, Mike Parker wrote: Many thanks to Rainer for his insightful new article for the D Blog outlining the new name mangling algorithm. He talks about the old implementation and its limitations before going into the details of the new one. It's a topic I had never considered digging into before, even when the big Voldemort issue first popped up, but now I find it interesting. The blog https://dlang.org/blog/2017/12/20/ds-newfangled-name-mangling/ Reddit https://www.reddit.com/r/programming/comments/7l1h36/ds_newfangled_name_mangling/ I really enjoyed this! Typo: "This is were I stepped in..." -> "..where.."
Re: Munich D Meetup December 2017
Reminder for tonight! On Monday, 4 December 2017 at 21:30:07 UTC, Dragos Carp wrote: On December 20th, with the title "D School" we will have our next Munich meetup. Come as beginner and we assist you during a self-guided course. Come as advanced and we review your library or polish your PR. Please RSVP on: https://www.meetup.com/de-DE/Munich-D-Programmers/events/245624091/ Thanks, Dragos
D's Newfangled Name Mangling
Many thanks to Rainer for his insightful new article for the D Blog outlining the new name mangling algorithm. He talks about the old implementation and its limitations before going into the details of the new one. It's a topic I had never considered digging into before, even when the big Voldemort issue first popped up, but now I find it interesting. The blog https://dlang.org/blog/2017/12/20/ds-newfangled-name-mangling/ Reddit https://www.reddit.com/r/programming/comments/7l1h36/ds_newfangled_name_mangling/
Re: D Ebooks On Sale For $5 Each
On Wednesday, 20 December 2017 at 13:40:29 UTC, Kyle wrote: Your book and Adam's are both excellent and this looks like a prime opportunity to try out Kai's. Thanks! Absolutely, pick up Kai's book. I wish it had been around when I wrote Chapter 10 in mine.
Re: D Ebooks On Sale For $5 Each
On Tuesday, 19 December 2017 at 23:57:24 UTC, Mike Parker wrote: Packt is having one of their sales right now. Each of their ebooks is $5. If you haven't gotten the D books yet, now's a great time to do so! https://www.packtpub.com/application-development/d-cookbook https://www.packtpub.com/application-development/learning-d https://www.packtpub.com/web-development/d-web-development Your book and Adam's are both excellent and this looks like a prime opportunity to try out Kai's.
Re: Beta 2.078.0
I think https://issues.dlang.org/show_bug.cgi?id=18047 is also fixed in 2.078. It was fixed in https://github.com/dlang/phobos/pull/5911, but it is not shown in the changelog. https://issues.dlang.org/show_bug.cgi?id=17459 was also fixed in the same PR and it is shown in the changelog. Could you investigate this please?
Re: Beta 2.078.0
Please check this https://issues.dlang.org/show_bug.cgi?id=18100
Re: Blog post: using dynamic libraries in dub
On Wednesday, 20 December 2017 at 08:09:53 UTC, Martin Nowak wrote: At some point `dub build` should get a `--shared` option to change the meaning of `library` target types from `staticLibrary` to `dynamicLibrary`. The shared libs could be linked with absolute paths. Would this work in all cases? Do tls variables work across Linux shared libraries? Do we expect all dub libraries to have correct export annotations once export goes live?
Re: Blog post: using dynamic libraries in dub
On 12/19/2017 06:58 PM, Neia Neutuladh wrote: > From the "it's a hacky workaround but it's what we've got" department: > how to use dynamic libraries in dub, with GtkD as the example. At some point `dub build` should get a `--shared` option to change the meaning of `library` target types from `staticLibrary` to `dynamicLibrary`. The shared libs could be linked with absolute paths. http://code.dlang.org/package-format?lang=sdl#target-types https://github.com/dlang/dub/issues/571
