Antonio Mallia

@mavam do we want to use Boost::serialization here? If not, lets clarify if we want binary serialization or human-readable serialization with `operator>>` & `operation

> Adding a Boost dependency just for serialization would be overkill. I would like to keep the dependencies as minimal as possible: CMake plus a C++11 compiler. Actually, I think...

Oh, this is cool! This will allow to have any type hashable and so able to add to a BF. From my understand currently only arithmetic types (and arrays or...

This should also work even if not ideal with `std::atomic`. ```cpp struct my_type { BEGIN_VISITABLES(my_type); VISITABLE(int, a, 0); VISITABLE(float, b, 0.0); VISITABLE(std::string, c); VISITABLE(std::atomic, d, {0}); END_VISITABLES; }; ``` What...

We can always think about having `VISITABLE`, `VISITABLE_INIT` and `VISITABLE_LISTINIT`. ```cpp struct my_type { BEGIN_VISITABLES(my_type); VISITABLE_INIT(int, a, 0); VISITABLE_INIT(float, b, 0.0); VISITABLE(std::string, c); VISITABLE_LIST(std::atomic, d, {0}); END_VISITABLES; }; ```

Yes! You totally got my point. I just called them differently: `VISITABLE_INIT` and `VISITABLE_LISTINIT` but the idea is the same. I actually like your naming better. I wouldn't bother too...

Could you let me know when the new feature is in place? Thank you

Thanks. Let me know if you want me to try it as well before you merge the change.

From my understanding `nodiscard` is used to enforce the programmer to use the returned value of a function. For example, this can be useful when an error is returned and...

> Why two of the tests don't find OpenMP but the rest does? In this case we need to make OpenMP required and link to the target: ``` find_package(OpenMP REQUIRED)...