Three Cool Things About D - The Case for the D Programing Language
Why Stack Overflow recommends it
Stack Overflow users link it when asking about specific points the talk raises, such as D's garbage collection, scope(failure) error handling, the min implementation, and the std::endl fiasco.
Recommended by 0 people across 0 different months, 2010 to 2011.
What it is
A Google Tech Talk from July 2010 in which Andrei Alexandrescu, author of Modern C++ Design, introduces the D programming language, its motivation and core tenets. He pitches D as a successor to C++ that handles high-performance systems work while also competing with higher-level languages.
What people said
Cites Matthieu N. · 2010-11 · Stack Overflow · on “Correct implementation of min”
At time 0:43:15 in this Tech-Talk about D [this video] , The implementation of the min function is discussed. Concerns about "stability" and "extra shuffling (if values are equal)" when being used in some algorithm(s) is proposed as one of the reasons for the implementation shown. Can anyone provide a real/practical use-case (or provide a more detailed explanation) where this specific implementation of min is "stable" (aka better) as opposed to its other possible implementation? Or is this just another example of alpha-geeks going a bit too far? Recommended implementation: template <class LHS, class RHS, class Return> inline Return min(LHS& lhs, RHS& rhs) { return (rhs < lhs) ? rhs : lhs; } Other
Cites user34537 · 2011-01 · Stack Overflow · on “Alternative to catch in D?”
I am watching Three Cool Things About D - The Case for the D Programing Language [this video] and it basically says dont use try/catch/finally (about the 38mark. 39:30 says you dont want to look at the try/catch it generates), its much nicer to use scope(failure) (theres also exit and success). My question is what happens when you want to check the exception and do an action based on the exception such as alert the user the disk has no space or mark a url as 404 (.NET webclient/webrequest throws on this) or retry later if a 500 error code occurs. How would i do this? must i use try/catch or is there another way?
Cites Tod · 2011-03 · Stack Overflow · on “What is the C++ iostream endl fiasco?”
I was listening to a google talk by Andrei Alexandrescu on the D programming [this video] language when he threw out a one liner about the "endl" fiasco. I just thought endl was the preferred way to signify the end of a line and flush the buffer for a stream. Why is it considered a fiasco? Should I not be using it in my code?
Cites Nordlöw · 2011-09 · Stack Overflow · on “To GC or Not To GC”
I've recently seen two really nice and educating languages talks: This first one [LINK] by Herb Sutter, presents all the nice and cool features of C++0x, why C++'s future seems brighter than ever, and how M$ is said to be a good guy in this game. The talk revolves around efficiency and how minimizing heap activity very often improves performance. This other one [this video] , by Andrei Alexandrescu, motivates a transition from C/C++ to his new game-changer D . Most of D's stuff seems really well motivated and designed. One thing, however, surprised me, namely that D pushes for garbage collection and that all classes are created solely by reference . Even more confusing, the book The D Programming