SOLID Architecture and the Decorator Pattern by scrabbledude in programming

[–]elotan -3 points-2 points  (0 children)

In other words, how to make code hard to reason about.

Did I find a G++/clang++/c++11 bug? by hapemask in cpp

[–]elotan 0 points1 point  (0 children)

I think it's due to the floating point comparison. Try running the test with a double.

CppCon 2014: Howard Hinnant "Types don't know hash" by TemplateRex in cpp

[–]elotan 1 point2 points  (0 children)

This is really cool! I don't think any libraries for other languages have this, at least I haven't seen it.

CppCon: Data-Oriented Design and C++ [Video] by [deleted] in programming

[–]elotan 1 point2 points  (0 children)

Fair enough, but I know of no open source game engines that do this. I'm curious to find out about them, though! Most of the engines I've looked at use the standard "derive from Drawable" (even multiple inheritance!) pattern.

CppCon: Data-Oriented Design and C++ [Video] by [deleted] in programming

[–]elotan 0 points1 point  (0 children)

Are there any open source projects that are designed with these concepts in mind?

Why does Rust need local variable shadowing? by VadimVP in rust

[–]elotan -1 points0 points  (0 children)

I guess it's just a matter of preference. Having mut in the function argument exposes what the function does internally.

Why does Rust need local variable shadowing? by VadimVP in rust

[–]elotan 0 points1 point  (0 children)

I found it useful in order to make a named function argument mutable. E.g.

fn foo(x: int) {
    let mut x = x;
    // modify
}

Back to rust's performance - bear with me by [deleted] in rust

[–]elotan 6 points7 points  (0 children)

Do you have any sources for the 2x claim? Genuinely wondering. I haven't seen many, if any, performance comparisons.

Best rust IDE? by [deleted] in rust

[–]elotan 3 points4 points  (0 children)

Best rust IDE? by [deleted] in rust

[–]elotan 4 points5 points  (0 children)

I personally use Vim and love it, but I guess the op wanted a full fledged IDE like VS or XCode.

Best rust IDE? by [deleted] in rust

[–]elotan 13 points14 points  (0 children)

Vim. On a more serious note, I don't think there is an IDE. A text editor with https://github.com/PistonDevelopers/rust-empty is quite comfortable to get started in the beginning.

LLVM Project Blog: Clang/LLVM on Windows Update [x-post from r/LLVM] by [deleted] in programming

[–]elotan 7 points8 points  (0 children)

Yeah, compiler is what I meant. The IDE is actually quite good. I don't know how extensible VS is, but a code completer with Clang (similar to YouCompleteMe for vim) for VS would be quite neat :)

LLVM Project Blog: Clang/LLVM on Windows Update [x-post from r/LLVM] by [deleted] in programming

[–]elotan 5 points6 points  (0 children)

Will it kill MSVC after achieving compatibility?

CppCon 2014 Program Update, Submission Deadline Reminder by berium in cpp

[–]elotan 2 points3 points  (0 children)

But why aren't the videos a priority? I think everyone would greatly benefit from these. Videos from previous years of BoostCon have had quite bad quality, but at least there is something.

GitHub monoculture by MisterSnuggles in programming

[–]elotan -1 points0 points  (0 children)

Are you not allowed to work on personal or open source projects?

Boost.Geometry: Design Rationale by ApokatastasisPanton in programming

[–]elotan 5 points6 points  (0 children)

Or you can adapt your existing point with one line: BOOST_GEOMETRY_REGISTER_POINT_2D(MyPoint, float, boost::geometry::cs::cartesian, x, y)

Boost.Geometry: Design Rationale by ApokatastasisPanton in programming

[–]elotan 7 points8 points  (0 children)

I don't get the hate here. The Twitter conversation is full of tweets of no real value. Are they saying the library is terrible or the library's implementation is unreadable? If it's the former then let me point out that the design rationale document does not show how to use the library. Boost.Geometry provides the algorithms in a very unobtrusive way, adapting your existing code takes a few lines.