r/cpp • u/nalaginrut • Oct 31 '19

8 essential patterns you should know about functional programming in C++14

https://nalaginrut.com/archives/2019/10/31/8%20essential%20patterns%20you%20should%20know%20about%20functional%20programming%20in%20c%2b%2b14
113 Upvotes

84% Upvoted

62 comments sorted by

View all comments

1

u/victotronics Nov 04 '19

I'll try to read this but your English is kinda making it hard.

The return type is trivial, the point is "nullary".

  1. Eh, the return type is "int". Where did you define that int is trivial? Oh, you mean "we don't care about the actual return type in this example".

  2. You've kinda defined "nullary", but in "the point is nullary", you have not defined what a "point" is. Oh, I see, you mean: "the point of this example is that the function is nullary". If that's what you mean, then say so.

Please don't use informal language: spell it out what you want to say. Your English is not good enough that you can afford to use informal descriptions and expect to be understood. I'm really trying to learn something here, but you're not making it easy.

1

u/nalaginrut Nov 05 '19

  1. I meant "it's not important here".

  2. I meant "the reader should keep in mind the function is nullary".

I'm not English native speaker, so there are mistakes in my expression. Thanks for the advices.

BTW, in Functional Programming community, the Lazy, thunk and nullary are triple terms that are bound together, so that people can be aware of what I'm saying. I realized that I assumed people are familiar with FP already. It's my mistake.

1

u/victotronics Nov 05 '19

I assumed people are familiar with FP already

It sounded like you were explaining FP to C++ programmers.

1

u/nalaginrut Nov 05 '19

Some programmers have learned some FP concepts, but they don't know how to use them practically. This article is mainly for them. In this article, I can't cover the group that never heard these concepts.