Reviewer source(s):
cjg...@chromium.org is from context(googleclient/chrome/chromium_gwsq/team/topchrome/config.gwsq)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Thanks for adding this - it addresses what feels like a primary oddity and pain point in Kombucha.
void FreeTemporaryValue(TemporaryIdentifier<V> variable) {Naming: Why Free vs. Reset or Release? Is this a homage to C? Modern C++ coders are conditioned to bristle at the word "free".
DECLARE_UNIQUE_IDENTIFIER_TYPE(InteractiveTestTemporaryIdentifier);With anything Kombucha, the API tends to be clean and simple, but under the hood, there's a bunch of complexity. Can you include class-level comments on the pieces in here, to cover things like (eg) why does an identifier need to be templated? Doesn't have to be a novel, but "some" comments would be better than none, for someone who wants to dig into this later.
INTERACTIVE_TEST_TEMPORARY_VALUE(int, kIntVariable);Naming nit: After reading this CL a couple times, why "temporary"? Everything's temporary in a context like this. My mind went for just INTERACTIVE_TEST_VALUE(), with SetTestValue() and GetTestValue() for accessing them. Or even SetValue() and GetValue(). Would that be too ambiguous with base::Value? What made you use "Temporary"?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
void FreeTemporaryValue(TemporaryIdentifier<V> variable) {Naming: Why Free vs. Reset or Release? Is this a homage to C? Modern C++ coders are conditioned to bristle at the word "free".
BTW, this doesn't have to change; just food for thought.