Clarify ToggleState states
Rewrite the comment so it's easier to read.
Change-Id: I41d61178b94aa31b4e11185f8af748e3501d408c
Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/139905
Reviewed-by: Corentin Wallez <cwallez@chromium.org>
Kokoro: Kokoro <noreply+kokoro@google.com>
Commit-Queue: David Neto <dneto@google.com>
diff --git a/src/dawn/native/Toggles.h b/src/dawn/native/Toggles.h
index 4259841..64b4be2 100644
--- a/src/dawn/native/Toggles.h
+++ b/src/dawn/native/Toggles.h
@@ -128,8 +128,13 @@
}
// TogglesState hold the actual state of toggles for instances, adapters and devices. Each toggle
-// is of one of these states: set/default to enabled/disabled, force set to enabled/disabled, or
-// left unset without default value (and thus implicitly disabled).
+// is in of one of these states:
+// - set
+// - defaulted to enable
+// - disabled
+// - force set to enabled
+// - force set to disabled
+// - unset without default (and thus implicitly disabled).
class TogglesState {
public:
// Create an empty toggles state of given stage