haptork / easylambda Goto Github PK

Would you like to replace any double quotes by angle brackets around file names for include statements?

does thie project surpport vc2015 on windows?

I suggest to reuse a higher level build system than your current small make file so that powerful checks for software features will become easier.

• CMake
• Autotools

It's a bad idea to apply std::move when returning a local object. Scott Meyer says: "Never apply std::move or std::forward to local objects if they would otherwise be eligible for the return value optimization" (Effective Modern C++)

The idea is that the compiler can optimize away the copy if you return by value, but if it can't, it must move. If you apply std::move then it has to move in either way. You're preventing RVO from happening.

I saw this in a few places around the code: https://github.com/haptork/easyLambda/search?q="return+std%3A%3Amove"&type=Code

I expect that exception handling is usually supported by a C++ program. I wonder why your function "main" does not contain corresponding try and catch instructions so far.

How do you think about recommendations by Matthew Wilson in an article?

Would you like to adjust the implementation if you consider effects for uncaught/unhandled exceptions like they are described by Danny Kalev?

Addition of UDFs in algorithms that plot and animate rows as they stream in a map unit, possibly using Cinder.

Since there is a good support for loading data and column selection, this can be quite useful and fits naturally.

However, it goes against the fact that plotting and analysis are two separate things, so I don't know how good of an idea this is.

Hi - Thank you for the excellent library. Looks very interesting. Do you have any plans of adding instructions for pre-requisites and compilation instructions on Windows (e.g., using MSVC 2015)?

An extra null pointer check is not needed in a function like the destructor for the class "DumpFile".

I would like to point out that identifiers like "__ezl__EZL__H__" and "__FILTERBUILDER_EZL_H__" do eventually not fit to the expected naming convention of the C++ language standard.
Would you like to adjust your selection for unique names?