FunctionalPlus VS pipes

Hoogle is really amazing!

Inspired by it, I implemented something similar for FunctionalPlus (a functional-programming library for C++): https://www.editgym.com/fplus-api-search/

I'd love to see more projects taking this path too. :)

You can get a feel for it on its api search site: as an example, enter these queries:

I use a library called FunctionalPlus daily.

As idiomatic, I will try to adopt as much as possible purely functional programming in C++ by using https://github.com/Dobiasd/FunctionalPlus . Do you have by any chance any alternative suggestion?

Any project CML file that is more complex than this is mismanaged and needs fixing asap. There is absolutely no reason to make CML files describing requirements of a library substantially more complex other than if you have a vendetta against yourself, package maintainers and your users.

FunctionalPlus - 30 lines for usage requirements + 60 for install rules: just simple commands creating a target, setting properties and defining install rules. Hmm, nothing unholy here.

Another option is to use a superbuild CML where you can do all the nasty, platform specific things. Example of a superbuild CML.

You can copy this project structure: https://github.com/Dobiasd/FunctionalPlus

C++ ranges may not be as nice and clean as, say, Rust iterators, but they’re still flat and semantic, and that’s a huge improvement over the unreadable imperative cancer that is for loops. If you don’t like them, another option is joboccara/pipes.

There are already joboccara/pipes for that.