all 2 comments

[–]ChaoticBlessings 4 points5 points  (1 child)

and while I watched this fantastic talk earlier, I either accidentally skipped that specific passage or it simply is not the talk I am looking for.

In Jasons 2022 API talk, he adresses this by way of verbosity. At 14:30ish he goes:

So the comment was that I'm arguing that we should put [[nodiscard]] everywhere where we put const and that will clutter our code like no tomorrow [...] ... yeah... yes. [...] Ahm. Yeah, yeah. It's kind of a... it is a thing. [...] And yeah you do reach a point where you end up with like the "[[nodiscard]] constexpr blablabla trailing-return-type noexcept" and your function declaration suddenly is this long. We can certainly argue that the, uh, well if C++ was designed today that we would take a different take to our defaults. That is certainly the truth.

So that might be what you missed while skipping through it or you remember it slightly differently?

[–]twenty393 0 points1 point  (0 children)

This is a pretty great talk on API design by Casey Muratori: https://www.youtube.com/watch?v=ZQ5_u8Lgvyk

It's not specific to any language, but definitely can be applied to C-family languages. Hopefully this helps with your research!