I agree that report and record are different. To me record means it’s preserved in some managed way.
The implementation has the ability to vary quite widely from simply printing to stdout, logging to a file, writing to a queue / database, and yet the same name will continue to reflect all those possibilities
This makes it sound like the intent goes beyond logging, but not so far as recording. That’s how I come to ‘report’ as the correct verb.
Agreed, report feels clearer as the verb “record” is more about permanent storage and later reference.
Or even just reportMissing? Depending on what’s happening around call sites, I often find I can drop generic stuff like “Data” and it’s just as clear, especially when looking at a function signature.
For instance:
I would use
reportMissingDataSee, both
reportandrecordsignify different things in my mind. The original code was justprinting to stdout.In my mind
logMissingDatamakes more sense because it’s not actively sending anything; it’s just logging.I agree that report and record are different. To me record means it’s preserved in some managed way.
This makes it sound like the intent goes beyond logging, but not so far as recording. That’s how I come to ‘report’ as the correct verb.
Agreed,
reportfeels clearer as the verb “record” is more about permanent storage and later reference.Or even just
reportMissing? Depending on what’s happening around call sites, I often find I can drop generic stuff like “Data” and it’s just as clear, especially when looking at a function signature. For instance: