Re: [PATCH v2 1/7] negotiator/null: add null fetch negotiator
- From
Derrick Stolee <stolee@gmail.com>
- Date
- Aug 12, 2020, 12:55 UTC
- Message-ID
- <2f6b3e7e-8f83-bfde-ab63-1eed08ff32b5@gmail.com>
- In-Reply-To
- <35bdd372ae3691f54775dd616576e8ed6d68f1d3.1597184949.git.jonathantanmy@google.com>
On 8/11/2020 6:52 PM, Jonathan Tan wrote:
> Add a null fetch negotiator.
I understand the value of this negotiator. I'm concerned about using "null" as the name, since it has a clear relationship to zero-valued pointers and that's not what is happening. (My gut feeling starting the patch was that some function pointers would be NULL or something.)
Instead, might I recommend "noop" or "no_op" in place of "null" here?
Thanks, -Stolee