Re: From the D Blog: A Pattern for Head-mutable Structures
On Saturday, 27 June 2020 at 16:02:53 UTC, Paul Backus wrote: On Saturday, 27 June 2020 at 15:06:12 UTC, Avrina wrote: Do you understand what prioritizing is? Fake internet points are being prioritized over ease of access to the community. Another way to frame it is that "respecting the rules of another community (HN) is being prioritized over a minor convenience for the D community." If we would like others to treat the D community with respect, I think it is only fair that we treat their communities with respect as well. +Paro https://en.wikipedia.org/wiki/History_of_large_numbers
Re: From the D Blog: A Pattern for Head-mutable Structures
On Saturday, 27 June 2020 at 15:06:12 UTC, Avrina wrote: On Saturday, 27 June 2020 at 02:42:13 UTC, Andrei Alexandrescu wrote: On 6/26/20 1:02 PM, Avrina wrote: On Friday, 26 June 2020 at 13:35:20 UTC, Andrei Alexandrescu wrote: On 6/26/20 9:03 AM, Avrina wrote: [...] From https://wiredcraft.com/blog/how-to-post-on-hacker-news/: "Direct links to the post don’t allow people to vote. The link we have at the bottom of the post for example (http://news.ycombinator.com/item?id=5200847) won’t work for upvoting. We need upvotes to be made from the newest page or the front page." "It says a lot about the priorities when you can't even get a simple link, community comes last." There's some massive misunderstanding here. Do you understand the reason he did not a post a simple link? Do you understand what prioritizing is? Fake internet points are being prioritized over ease of access to the community. Words are powerful, they kindle emotions. Saying for everyone here. Async communication gives an opportunity for everyone to throw in sharp words. We wouldn't be saying such words when we meet them in person. I regret being the person to start this. Now this thread is going in a different direction. Let the bitterness end here please!!
Re: From the D Blog: A Pattern for Head-mutable Structures
On Friday, 26 June 2020 at 13:03:01 UTC, Avrina wrote: On Friday, 26 June 2020 at 05:37:13 UTC, Arun Chandrasekaran wrote: On Thursday, 25 June 2020 at 11:55:14 UTC, Mike Parker wrote: I've also submitted it to HN (please use the search box): https://news.ycombinator.com/newest This is a very interesting post. But this strategy with HN is clearly not working. 5 upvotes after 17 hours and 0 comments. Please paste the direct link in future even if the ranking goes down after a few hours. Some publicity is better than nothing at all. Here. https://news.ycombinator.com/item?id=23639552 It says a lot about the priorities when you can't even get a simple link, community comes last. No, that's not right to say just for a hyperlink! Show some appreciation and kindness please. If we don't have anything nice to say, it's better not to say anything at all.
Re: From the D Blog: A Pattern for Head-mutable Structures
On Thursday, 25 June 2020 at 11:55:14 UTC, Mike Parker wrote: I've also submitted it to HN (please use the search box): https://news.ycombinator.com/newest This is a very interesting post. But this strategy with HN is clearly not working. 5 upvotes after 17 hours and 0 comments. Please paste the direct link in future even if the ranking goes down after a few hours. Some publicity is better than nothing at all.
Re: Blog Post: Beating std::visit Without Really Trying
On Saturday, 5 October 2019 at 02:59:58 UTC, Paul Backus wrote: I was curious how C++17's std::variant compared to the options we have in D, like Algebraic and SumType, so I did a simple comparison of the generated assembly for each of them. You can read about it at the link below. And as you can probably guess from the title, D comes out ahead, in the end. https://pbackus.github.io/blog/beating-stdvisit-without-really-trying.html This is my first attempt at sharing something like this, so any comment or feedback is very much appreciated! Good one. Any plans to push SumType as a replacement of Phobo's Algebraic?
Re: "D for a @safer Linux Kernel" poster presentation at APLAS
On Thursday, 3 October 2019 at 11:21:41 UTC, RazvanN wrote: On Thursday, 3 October 2019 at 07:13:05 UTC, Arun Chandrasekaran wrote: [...] It seems that they are creating a framework for developing kernel modules in rust that can be integrated with the linux kernel. They haven't tested the performance of a particular rust driver compared to a C one. This is a bit different from what we did: we directly ported a C driver to D and integrated it with the kernel, with negligible performance loss. The 4% performance loss that was encountered in some situations is due to the fact that we have D wrappers over C function calls and some macros are translated as functions that are called at runtime - they are not inlined -; one thing we still need to do is to test with the recent link time optimizations (LTO) and profile guided optimizations (PGO) flags in clang; we are confident that this will enhance the performance of the ported driver). Good to know. May be you could publish the code on GitHub/GitLab and that could attract interest among people who care about performance to take a look. It's tricky to measure performance at this scale.
Re: "D for a @safer Linux Kernel" poster presentation at APLAS
On Friday, 27 September 2019 at 09:26:22 UTC, RazvanN wrote: Hello all, Alexandru Militaru's work "D for a @safer Linux Kernel" [1] has just been accepted for a poster presentation at APLAS [2]. We hope that this will be good publicity for D, Cheers, RazvanN [1] https://www.youtube.com/watch?v=weRSwbZtKu0 [2] https://conf.researchr.org/track/aplas-2019/aplas-2019-posters#About Nice. Has there been any recent performance improvements? There was a similar talk recently at the Linux Security Summit [1] yesterday from the Rust community. [1] https://www.youtube.com/watch?time_continue=1=RyY01fRyGhM
Re: GDB + ddemangle
On Friday, 20 April 2018 at 17:55:12 UTC, Iain Buclaw wrote: On 20 April 2018 at 17:40, drug via Digitalmars-d-announce wrote: 20.04.2018 16:49, Iain Buclaw пишет: [...] it works, thank you. But not in all cases. For example when gdb stops on breakpoint it demangle, but if I do `bt` - backtrace isn't demangled. Using a compiler that implements 2.077 or later (IIRC) probably won't, due to gdb being too old. They broke ABI by introducing back referencing, no release of gdb supports that yet. This stays broken after 1 year. How do we fix this?
Re: New and Unofficial OpenCV binding for D programming language
On Friday, 5 April 2019 at 15:52:42 UTC, Paolo Invernizzi wrote:
On Friday, 5 April 2019 at 13:19:22 UTC, Ferhat Kurtulmuş wrote:
On Friday, 5 April 2019 at 07:56:42 UTC, Paolo Invernizzi
wrote:
On Thursday, 4 April 2019 at 23:08:21 UTC, Ferhat Kurtulmuş
wrote:
[...]
Nice!
Version 3.x has an internal pointer in the mat struct, is
that changed with 4.x?
- Paolo
It still has it, if you what you mean:
Mat Mat_FromArrayPtr(int rows, int cols, int type, void* data){
return new cv::Mat(rows, cols, type, data);
}
No, I mean that the Mat structure has a MatSize MatStep member
with pointers to the struct data itself.
I was writing a binding to OpenCV 3.x a while ago and now I know
why I got blocked. :|
Re: New and Unofficial OpenCV binding for D programming language
On Thursday, 4 April 2019 at 23:08:21 UTC, Ferhat Kurtulmuş wrote: Hi folks! D is awesome, but it is a shame that there is no any opencv bindings for d yet. Actually we have it now :) Although I am a new dlang learner, I dared to do it: https://github.com/aferust/opencvd. C interface was taken from gocv, and the implementation has been highly influenced by gocv (maybe it is better to make git submodule it, since gocv project is being updated very often?). I admit that it is far from being a complete binding, but it is a beginning. I invite you lovely and pro dlang community to grow it. I did not want to add it to code.dlang.org before it become a better binding. Good work. Can you please mention about the version of Ubuntu you developed it on? Also looks like you have committed the cmake temporary build directory to git, you may want to git rm. :)
Re: Containerize Your D Server Application
On Thursday, 14 March 2019 at 12:38:30 UTC, Mike Parker wrote: One of the items on my list of "things I'd like to do if I only had the time" is to create a Mud server with D and deploy it with Docker. Just for kicks. If I ever do get around to it, my ignorance of all things Docker will not be the time sink it could have been thanks to this latest post on the D Blog by Kai Nacke. The Blog https://dlang.org/blog/2019/03/14/containerize-your-d-server-application/ Reddit https://www.reddit.com/r/programming/comments/b0zqck/containerize_your_d_server_application/ Can we make dub generate the docker container as well? CMake can do that. The usage would be simply ``` dub build -b release dub build docker
Re: LDC 1.13.0
On Sunday, 16 December 2018 at 15:57:25 UTC, kinke wrote: Glad to announce LDC 1.13: * Based on D 2.083.1. * The Windows packages are now fully self-sufficient, i.e., a Visual Studio/C++ Build Tools installation isn't required anymore. * Substantial debug info improvements. * New command-line option `-fvisibility=hidden` to hide functions/globals not marked as export, to reduce the size of shared libraries. Full release log and downloads: https://github.com/ldc-developers/ldc/releases/tag/v1.13.0 New Wiki page highlighting cross-compilation: https://wiki.dlang.org/Cross-compiling_with_LDC Thanks to all contributors! Excellent work. LDC has caught up with DMD on the stable! Self sufficient Windows build is possible because of MS stable ABI? Is it guaranteed to be stable hereafter? Thanks for all your work.
Re: dlang-requests 1.0.0
On Wednesday, 24 October 2018 at 14:30:57 UTC, ikod wrote: Hello, 1.0.0 release adds "Interceptors" (or middleware). You can instrument whole library or single request with logging, modifying, caching methods without changes in your (or this library) code. Together with configurable "socket fabric" it gives more control over request execution when you need it. [...] Thanks you! dlang-requests is a fantastic library.
Re: LDC 1.12.0-beta1
On Tuesday, 4 September 2018 at 22:47:39 UTC, kinke wrote: Glad to announce the first beta for LDC 1.12: * Based on D 2.082.0. * LTO working for Win64 targets. * IR-based PGO working for Windows targets. Full release log and downloads: https://github.com/ldc-developers/ldc/releases/tag/v1.12.0-beta1 Thanks to all contributors! Fantastic work! This is the first time LDC caught up with DMD in a single day, I guess.
Re: GDC with D frontend 2.081.2
On Monday, 27 August 2018 at 20:03:28 UTC, Iain Buclaw wrote: On 27 August 2018 at 20:59, Arun Chandrasekaran via Digitalmars-d-announce wrote: On Monday, 27 August 2018 at 17:44:01 UTC, Iain Buclaw wrote: On 27 August 2018 at 19:23, Arun Chandrasekaran via Digitalmars-d-announce wrote: [...] Version print information is managed outside of gdc. You can get this from __VERSION__ or output of -v [...] Ask dub maintainers why. [...] Raise a bug then? Iain. Should I raise it at https://bugzilla.gdcproject.org ? ``` User account creation has been restricted. Yes, due to high number of spam account on google mail, account creation is limited for people coming from that domain. https://bugzilla.gdcproject.org/show_bug.cgi?id=305
Re: GDC with D frontend 2.081.2
On Monday, 27 August 2018 at 17:44:01 UTC, Iain Buclaw wrote: On 27 August 2018 at 19:23, Arun Chandrasekaran via Digitalmars-d-announce wrote: [...] Version print information is managed outside of gdc. You can get this from __VERSION__ or output of -v [...] Ask dub maintainers why. [...] Raise a bug then? Iain. Should I raise it at https://bugzilla.gdcproject.org ? ``` User account creation has been restricted. Contact your administrator or the maintainer (ibuc...@gdcproject.org) for information about creating an account. ```
Re: GDC with D frontend 2.081.2
On Friday, 24 August 2018 at 05:35:13 UTC, Eugene Wissner wrote:
As some of you may know D frontend was merged into GDC some
time ago and is up to date. D version currently supported by
GDC is 2.081.2 and it can be found in "gdc-7" and "gdc-8"
branches. I will say a bit more about GDC development and
development plans later.
I prepared GDC/GCC 7.3.0 binaries for x86-64 Linux built on
Ubuntu 18.04:
https://download.dlackware.com/gdc/gdc-7.3.0_2.081.2-linux-x86_64.tar.xz
I’m not a regular Ubuntu user, and built GDC in a VM, so don't
blame me (too much) if something doesn’t work, but let me know
anyway. For testing I've used a minimal Ubuntu installation and
had to install only "libc-dev" package. The package includes
gcc, g++, gdc and standard GNU tools, but no D tools like dub.
I still need some time to automate the building, then I can
build for more platforms and provide some core tools.
We support several GCC versions and we still support
C++-frontend (D version: 2.076). The reason for this is that
C++-frontend should be merged into the next GCC version (GCC
9), then it can be built without another D compiler. D frontend
goes into GCC 10 and can be built with GCC 9, so GCC can be
bootstrapped without external compilers and can be used to
bootstrap other D compilers.
Current branch model. There are 2 "master" branches: master and
stable. master contains D frontend and follows DMD master
(we'll see if we can update every week or every two weeks).
stable contains C++ frontend which doesn't get new D features
anymore but of course we merge bug fixes from master. Both
follow GCC master (master is updated weekly to GCC snapshots,
stable from time to time).
stable has 4 derivates: gdc-8-stable, gdc-7-stable,
gdc-6-stable and gdc-5-stable. It seems to be a lot, but the
last merge from stable was really trivial, so the most work is
done on the master derivates: "gdc-8" and "gdc-7" branches.
These two follow DMD stable and contain stable D releases.
1. It would be good to print the DMD frontend version with `gdc
--version`. It is helpful in reporting bugs. LDC does this.
```
$ ldc2 --version
LDC - the LLVM D compiler (1.9.0):
based on DMD v2.079.1 and LLVM 6.0.0
built with LDC - the LLVM D compiler (1.9.0)
Default target: x86_64-unknown-linux-gnu
Host CPU: ivybridge
http://dlang.org - http://wiki.dlang.org/LDC
Registered Targets:
aarch64- AArch64 (little endian)
aarch64_be - AArch64 (big endian)
arm- ARM
arm64 - ARM64 (little endian)
armeb - ARM (big endian)
nvptx - NVIDIA PTX 32-bit
nvptx64- NVIDIA PTX 64-bit
ppc32 - PowerPC 32
ppc64 - PowerPC 64
ppc64le- PowerPC 64 LE
thumb - Thumb
thumbeb- Thumb (big endian)
x86- 32-bit X86: Pentium-Pro and above
x86-64 - 64-bit X86: EM64T and AMD64
```
2. I see a file dub_platform_probe-UUID.s getting created in the
root dir when building with GDC and not with DMD/LDC.
3. Multiple definition error. Logs:
https://bpaste.net/show/7b12dfccceb1 This doesn't seem to be a
problem when building with DMD (v2.081.1) / LDC (1.9.0)
"dependencies" : {
"darg": "~>0.0.4",
"painlessjson": "~>1.3.5",
"requests": "~>0.8.3"
}
Re: Encouraging preliminary results implementing memcpy in D
On Wednesday, 13 June 2018 at 06:46:43 UTC, Mike Franklin wrote: I had a little fun today kicking the crap out of C's memcpy with a D implementation. https://github.com/JinShil/memcpyD Request for help: I don't have a Linux system running on real hardware at this time, nor do I have a wide range of platforms and machines to test with. If you'd like to help me with this potentially foolish endeavor, please run the program on your hardware and send me the results. Feedback, advise, and pull requests to improve the implementation are most welcome. Mike On 8 core, 16 GB Intel Skull Candy box running Ubuntu 18.04 64 bit. https://gist.githubusercontent.com/carun/f7c2c200b1be20d0a9489296d6601332/raw/db01bb8bc909c6048288fccc500bd15e5ee491b2/memcpyd-output.log Hope this helps.
Re: DConf 2018 Ex Post Facto
On Thursday, 31 May 2018 at 15:01:12 UTC, Mike Parker wrote: Since I returned home from my extended trip to Germany, it's been a slog trying to ramp back up into my usual routine. It was a week before I could find any words at all for a retrospective on the conference, and it very nearly took another week to get the post in readable form. I'm still not at peak productivity, but I'm getting there. I've got a couple of guest posts lined up (including one from Walter) and I should be getting the Twitter & FB feeds going again soon. In the meantime, here's what DConf 2018 was like from my perspective. The blog: https://dlang.org/blog/2018/05/31/dconf-2018-ex-post-facto/ Reddit: https://www.reddit.com/r/d_language/comments/8nj1nn/dconf_2018_ex_post_facto/ Thanks. This better utilizes the screen space on mobile[1]. Much easier to read than the previous posts[2] where the D logo hogged the screen. [1] https://imgur.com/a/c2jkSyq [2] https://imgur.com/jkJ8IFc
Re: Article: Why Const Sucks
On Monday, 5 March 2018 at 13:48:23 UTC, Adam D. Ruppe wrote: Just a semantic note, it is "straitjacket". "straight" is like a non-wiggly line. "strait" means narrow or constricted. Thus, the straitjacket is a jacket that constricts your movement. Of course, using "straight" is such a common mistake it has become generally accepted... but still, I like being precise with my words. Programmers like precision, don't we! From Simon Tatham article about how to report bugs effectively: https://www.chiark.greenend.org.uk/~sgtatham/bugs.html "Above all, *be precise*. Programmers like precision."
Re: The Expressive C++17 Coding Challenge in D
On Tuesday, 13 February 2018 at 23:35:36 UTC, Seb wrote: Someone revived the Expressive C++17 Coding Challenge thread today and I thought this is an excellent opportunity to revive my blog and finally write an article showing why I like D so much: https://seb.wilzba.ch/b/2018/02/the-expressive-c17-coding-challenge-in-d It's mostly targeted at beginners as I explain many basic D features, but maybe it's helpful for beginners looking into D. It takes a lot of time and effort to write such quality content. Thanks for detailed explanations. // import std.algorithm, std.exception, std.format, std.range, std.stdio; Do you think it is worth mentioning about std.experimental.scripting in section 2? Syntax highlighting is missing in some snippets.
Re: dub release package
On Tuesday, 23 January 2018 at 00:24:46 UTC, Seb wrote: Also please don't post questions to Announce! https://github.com/dlang/dub/issues would have been the right place. Ah, I thought I was posting to General. Sorry about that. I see similar posts though not often. The post creation page could hint to which forum we are posting, something like this: https://i.imgur.com/8LgLsx8.png
dub release package
I was looking at the recent DUB release for binary package of 1.7.1 at https://github.com/dlang/dub/releases The assets don't seem to contain the binary packages. Was it unnoticed or was it intentionally skipped?
Re: Interfacing D with C: Getting Started
On Wednesday, 6 December 2017 at 04:33:38 UTC, Mike Parker wrote: On Wednesday, 6 December 2017 at 04:27:01 UTC, Mike Parker wrote: On Wednesday, 6 December 2017 at 04:14:35 UTC, Arun Chandrasekaran wrote: [...] Why is this? How are we expected to write cross platform code with long/ulong? What are the alternatives? 99 It's right there in the blog post: import core.stdc.config : c_ulong, clong; Or was the paragraph ambiguous for you? long and ulong are always 8 bytes in D. It's the C types that vary across platforms. I've updated the text as Joakim suggested for clarity. Thanks Mike, that explains!
Re: Interfacing D with C: Getting Started
In D, long and ulong are always 8 bytes. This lines up with most 64-bit systems under the version(Posix) umbrella, where long and unsigned long are also 8 bytes. However, they are 4 bytes on 32-bit architectures. Moreover, they’re always 4 bytes on Windows, even on a 64-bit architecture. Why is this? How are we expected to write cross platform code with long/ulong? What are the alternatives?
Re: Release D 2.077.0
On Friday, 3 November 2017 at 13:47:55 UTC, Mike Parker wrote: On Thursday, 2 November 2017 at 22:35:03 UTC, Martin Nowak wrote: Glad to announce D 2.077.0. This release comes with a new, more compact mangling, templated vector operations, reproducible dmd builds, and various fixes. Thanks to everyone involved in this . http://downloads.dlang.org/releases/2.x/2.077.0/ http://dlang.org/changelog/2.077.0.html The dlang.org website will get updated soon. -Martin Blog: https://dlang.org/blog/2017/11/03/dmd-2-077-0-released/ Mike, thanks for the blog post. Few lines about how the name mangling issue was addressed would've been interesting know on the blog. Reddit: https://www.reddit.com/r/programming/comments/7ajg71/dmd_20770_released/
Re: Godbolt.org: mir-algorithm was added
On Friday, 22 September 2017 at 03:51:36 UTC, Ilya Yaroshenko wrote: Mir Algorithm and Mir GLAS (glas is experimental) was added to https://d.godbolt.org by Johan Engelen. Thanks you, Johan! [...] Honestly, how do you guys understand these assembly instructions that's further optimized by the complier? Am I alone here?
Re: Open Methods: From C++ to D
On Wednesday, 30 August 2017 at 13:35:22 UTC, Jean-Louis Leroy wrote: On Wednesday, 30 August 2017 at 04:48:11 UTC, Arun What was your rationale for `openmethod` instead of just `method`? Just that `openmethod` precisely expresses it's intent and `method` is too generic.
Re: Open Methods: From C++ to D
On Tuesday, 29 August 2017 at 12:45:50 UTC, Jean-Louis Leroy wrote: On Tuesday, 29 August 2017 at 12:09:01 UTC, Mark wrote: Nice. This does seem superior to the visitor pattern. Here is another example - AST traversal: https://github.com/jll63/openmethods.d/blob/master/examples/acceptnovisitors/source/app.d Thanks for this library. Just a suggestion. Would it possible to use `@openmethod` instead of `@method`?
Re: Project Highlight: Funkwerk
On Friday, 28 July 2017 at 13:37:31 UTC, Mike Parker wrote: They also chose Tango over Phobos, primarily because Tango provided logging and HTTP facilities What are they using for HTTP now?
Re: Snowflake Strings
On Wednesday, 22 February 2017 at 13:08:13 UTC, Mike Parker wrote: Blog post: http://dlang.org/blog/2017/02/22/snowflake-strings/ Thanks for a wonder article. PS: The blog UI may need to be corrected for browsing from mobiles[1]. [1] http://imgur.com/a/7IPkm
Re: Boston D Meetup 2/9: `shared` Experiences
On Saturday, 18 February 2017 at 00:08:28 UTC, Steven Schveighoffer wrote: On 1/30/17 4:48 PM, Steven Schveighoffer wrote: Attention fellow Boston D enthusiasts: I have set up a meetup for February, and Michael Coulombe will give a presentation on his experiences with shared. As before, this will be at the Capital One Cafe in the back bay (across from Prudential center). Hope to see you all there! https://www.meetup.com/Boston-area-D-Programming-Language-Meetup/events/237324049/ Here is the live stream: https://www.youtube.com/user/kirsybuu/live -Steve This is a nice talk. Thanks for sharing!
Re: Questionnaire
On Wednesday, 8 February 2017 at 18:27:57 UTC, Ilya Yaroshenko wrote: 1. Why your company uses D? a. D is the best b. We like D c. I like D and my company allowed me to use D d. My head like D e. Because marketing reasons f. Because my company can be more efficient with D for some tasks then with any other system language We don't use D. But IMO, D is the best PL with it's amazing compile time features (templates, templates everywhere and still it can be maintainable). 2. Does your company uses C/C++, Java, Scala, Go, Rust? C, C++, C#, Java 3. If yes, what the reasons to do not use D instead? 1. For algorithms: We develop biometric algorithms and create shared objects and DLLs. We need these to be used on variety of platforms interfacing with various languages like C++, C#, Java, Go. D makes it impossible to convince teams that develop algorithms. 2. For applications/solutions: An year ago we evaluated D (to replace C++) for one of our large scale distributed solution (map-reduce for biometrics). But ended up developing it in C++ for the following reasons: a) Lack of high quality libraries like Boost/Qt. With the horrible template syntax of C++, people created Boost and helped shape C++ what it is now. D is pleasant to program with and I'm wondering why there is no such comprehensive set of libraries in D. b) GC. We fill pretty much the entire RAM (>=128 GB) with data and operate on it. The end-to-end system latency must be in milliseconds and also provide high throughput. Not really an option with D's current state of GC. c) IDE support. d) We have already got used to the warts of C++, Java and we know how to avoid them. It is fair for us to ask the team to learn D, but not *ignore X and get used to it* as well. D tries to compete and satisfy all paradigms (recently trying to catch-up with Rust's safety feature) which is good from a language point of view. But it could also focus on fixing it's base. 2. Have you use one of the following Mir projects in production: No. 4. Have you use one of the following Tamedia projects in your production: No. 5. What D misses to be commercially successful languages? a) Good quality libraries b) Cross platform IDE c) Corporate backup c) Vibrant community. IMHO, the lack of good quality libraries can be directly attributed to the lack of critical mass of topnotch brains in the community. 6. Why many topnotch system projects use C programming language nowadays? a) Good quality libraries b) Small run-time c) Cross platform IDE d) People are already familiar with C/C++
Re: A New Import Idiom`
On Tuesday, 14 February 2017 at 23:01:42 UTC, Dmitry Olshansky wrote: On 2/14/17 3:32 AM, Jerry wrote: Anyways yes this is kind of cool and fascinating how it works, but that aside I hope I never see this used in phobos. Does anyone else feel this way? +1 Let's not make Phobos as scary as C++ STL. --- Dmitry Olshansky Honestly, after staring at C++ STL, I never imaged that the standard library of a language can be *readable* and *understandable* until I read phobos. Kudos to Walter, Andrei and contributors. I still believe that templated D code is much more readable and intuitive than templated C++ code. Arun
Re: vibe.d 0.8.0 and 0.7.31 beta releases
On Tuesday, 31 January 2017 at 11:11:28 UTC, Sönke Ludwig wrote: [1]: https://github.com/vibe-d/vibe-core Is vibe-core still in alpha stage? Github page says so.
Re: Vision document for H1 2017
On Wednesday, 4 January 2017 at 21:21:17 UTC, aberba wrote: I like the social media part. More people, more man power, more noise about D. I would read it as, with better signal-to-noise ratio.
Re: PostgreSQL native impl
On Tuesday, 3 January 2017 at 01:08:28 UTC, Chris Wright wrote: On Mon, 02 Jan 2017 20:29:55 +, Anton wrote: Today i spent about hour to write pure-D simple PostgreSQL driver for demonstration purposes. I was looking for developers interested in complete PostgreSQL driver (pure D) That demo not implements auth, therefore requires trusted user [1] https://github.com/anton-dutov/postgresql-native-d [2] https://www.postgresql.org/docs/9.6/static/protocol.html Nice! Looks like it wouldn't be much work to add prepared queries. I notice you rolled your own uri library. Might I point you toward urld? It supports ipv6 hosts (probably handy) and unicode domain names (nice to have, probably not useful here). http://code.dlang.org/packages/urld This is really neat! I've been looking for one such. I'm used to https://github.com/cpp-netlib/uri in C++.
Re: DIP 1003: remove `body` as a keyword
On Saturday, 19 November 2016 at 21:16:15 UTC, Dicebot wrote: DIP 1003 is merged to the queue and open for public informal feedback. PR: https://github.com/dlang/DIPs/pull/48 Initial merged document: https://github.com/dlang/DIPs/blob/master/DIPs/DIP1003.md If you want the change to be approved and have ideas how to improve it to better match on https://github.com/dlang/DIPs/blob/master/GUIDELINES.md and existing published reviews - please submit new PR with editorial and ping original author. Bump, if that makes sense.
