I am suggesting that a post whose answer is obvious -- from the documentation's text or examples (IOW, in the FM) -- strongly suggests that the poster has not RTFMed (or has not RTFMed will diligence).

In this context, the difference between perceiving a suggestion and an assumption, besides being too marginal to call or argue about, still misses the possibility that the OP has read the documentation and has simply misunderstood it or just didn't understand it at all.

I think that it is all too easy for those with long-term familiarity with the Perl docs to assume they are the very model of suffice and clarity, forgetting the struggles they themselves once had with them.

When I first came to Perl, despite 20 odd years of experience of other languages on several platforms, I found many parts of Perldoc to be quite opaque. Particularly because much of it assumes access to and familiarity with POSIX APi documentation. The assumption that "xxxxx() works the same way as xxxx() (2)" will mean something is rife in some parts of the docs.

And there are other parts that still go right over my head. Eg. The use of \G (and (?>...) for that matter ) in regexes. If I sit and read the docs and play in my REPL, I can usually, eventually make these constructs deliberately do something of my choosing. Usually. But you'll rarely if ever see me use them to solve real problems. I've simply never found the analogy or example that allows me to assimilate them into my way of thinking. As such, I've found other ways of solving the problems they are there to solve, and they do not figure into my approach to solving problems.

Concluding that an OPs failure to understand the relevant part of the docs is due to a lack of "due diligence", is assumptive in the extreme.