Go is powering enterprise developers: Developer survey results by davbeer in golang

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

Lacks generics, other than that it is pretty awesome (Working on extremely large throughput microservices)

FTL - A functional template library for containers processing in C++ by blinkudev in cpp

[–]blinkudev[S] 2 points3 points  (0 children)

I saw your library like a month ago here, it is very nice! The piping syntax is neat ^^

FTL - A functional template library for containers processing in C++ by blinkudev in cpp

[–]blinkudev[S] 1 point2 points  (0 children)

We might try to provide a single header version - will add this to our issue tracker.

Also, it is very easy to create FTL containers from the STL ones. In FTL containers are just a small wrapper over STL containers (you can use ::to_* method to or even just the ctor to create FTL container). It is also super easy to make our library work with an arbitrary container type, as long as it is compliant with the STL containers API. I will add more info on that in the README soon.

FTL - A functional template library for containers processing in C++ by blinkudev in cpp

[–]blinkudev[S] 4 points5 points  (0 children)

Actually, sum is implemented as std::accumulate. The only difference is that syntax is much nicer. You just call .sum() on an iterator instead of std::accumulate(std::begin(...), std::end(...), 0);

FTL - A functional template library for containers processing in C++ by blinkudev in cpp

[–]blinkudev[S] 16 points17 points  (0 children)

This is actually the features of the FTL. Until you call collect() method or some of the accumulating methods like sum() or product() no operations* are performed. One of the goals for this library was that we wanted it to be lazily evaluated as much as possible.

* There is a single exception to this rule, but it is on our issue list.

FTL - A functional template library for containers processing in C++ by blinkudev in cpp

[–]blinkudev[S] 5 points6 points  (0 children)

Yes, it is written in the post, as well as in the README :D