Rename timer `Setup` function to `Schedule`
This patch was motivated by my desire to fix a typo in the function
name. The noun "setup" is 1 word. The verb "set up" is 2 words. All
other member functions are verbs, so this one should be a verb too.
That means that the function should be called `SetUp`. During the
discussion that resulted from the rename, James Kuszmaul pointed out
that "setting up" a timer can be confusing. It implies that you can
only "set up" a timer once. But the intent is to let users set up
timers as many times as they like. So we decided on renaming the
function to `Schedule`. That conveys the purpose and intent better.
I took this opportunity to fix some other typos involving the verb
"set up".
Signed-off-by: Philipp Schrader <philipp.schrader@gmail.com>
Change-Id: I2f557d1f946960af82711f248820d5e2d385a5d3
diff --git a/aos/events/glib_main_loop_test.cc b/aos/events/glib_main_loop_test.cc
index 43f7c7a..aabab68 100644
--- a/aos/events/glib_main_loop_test.cc
+++ b/aos/events/glib_main_loop_test.cc
@@ -37,7 +37,7 @@
event_loop.Exit();
ran = true;
})
- ->Setup(event_loop.monotonic_now() + std::chrono::milliseconds(100));
+ ->Schedule(event_loop.monotonic_now() + std::chrono::milliseconds(100));
event_loop.Run();
EXPECT_TRUE(ran);
}
@@ -122,7 +122,7 @@
event_loop.Exit();
ran = true;
})
- ->Setup(event_loop.monotonic_now() + std::chrono::milliseconds(100));
+ ->Schedule(event_loop.monotonic_now() + std::chrono::milliseconds(100));
event_loop.Run();
EXPECT_TRUE(ran);
EXPECT_EQ(runs, 1);