Search Results

Firstly, given that you're using vector without namespace qualification (that is, not as std::vector), I assume you have a using namespace std; in this code. This is generally a bad idea, but especial …

Generally, I can't see any real problems, but there are a few things that I'm going to point out: In the assignment operator, you use std::swap(storage, rhs.storage) and declare it as noexcept. This …

Since begin() and rbegin() produce different (incompatible) types, the only way I could see of doing this would be to move the actual for_each into a template function. template <typename Iterator> v …

Firstly, some issues with API usage. Using raw std::threads is generally not the way you want to go with this sort of thing: prefer to use std::async. This also means you don't need to pass in by refe …

There are definitely some problems if you want to make this threaded. Firstly, access to m_searches is not protected in any way. Since this is a shared bit of memory, it would need to be protected by …

You can utilize std::transform here (I'll assume C++11 for the lambda): int main() { std::vector<uint8_t> first_list = {0x01, 0x10, 0x32, 0x1A}; std::vector<uint8_t> second; std::transfo …

I just wanted to chime in with the "lazy" (if not performant) way of doing this, using reverse iterators: bool is_palindrome(const std::string& s) { return s == std::string(s.rbegin(), s.rend()); …

Your design is a little bit confusing. You define your class as a template class, but just about everything takes and returns a double. Generally, you should try and be consistent: will this class wor …

Firstly, it's a good first attempt at writing some threaded code. The major sticking point is that you're passing in an int & and returning void. Of course, std::thread will just run some code and won …

Firstly, I'm not 100% sure how closely you want to follow the standard, but this is missing a (potentially significant) piece: what to do if the selection function throws an exception. From cppreferen …

I can't really speak to the portability of such code, as I honestly have no experience with anything other than IEEE754. Since you are targeting C++11, I can suggest that you can replace your compile- …

Generally, you should prefer to use std::async over naked use of threads. There are a few reasons for this: firstly, std::async can actually return a value (wrapped in a std::future), which means less …

The approach to doing this is two-fold. Firstly, you'll want to modify your classes to have a constructor taking an std::istringstream& as an argument. The second part will be to make a map of strings …

I actually quite like this pattern and use it relatively often. I'm not sure if there is something better than functors for this - if there is, I'm not really aware of it. That being said, with C++11, …

Let me restate the problem, because it wasn't 100% clear to me from what you've written. I personally think you've left out a bit too much code. I'll state my assumptions of what is going on, but idea …