From 3ee5ef12fb71be95d6e7f679900a497a2580d25e Mon Sep 17 00:00:00 2001 From: Alex Crichton Date: Thu, 24 Oct 2013 11:30:35 -0700 Subject: Remove the 'callback_ms' function from EventLoop This is a peculiar function to require event loops to implement, and it's only used in one spot during tests right now. Instead, a possibly more robust apis for timers should be used rather than requiring all event loops to implement a curious-looking function. --- src/libstd/rt/uv/uvio.rs | 9 --------- 1 file changed, 9 deletions(-) (limited to 'src/libstd/rt/uv') diff --git a/src/libstd/rt/uv/uvio.rs b/src/libstd/rt/uv/uvio.rs index 29370c484eb..eee89365fb5 100644 --- a/src/libstd/rt/uv/uvio.rs +++ b/src/libstd/rt/uv/uvio.rs @@ -222,15 +222,6 @@ impl EventLoop for UvEventLoop { } as ~PausibleIdleCallback } - fn callback_ms(&mut self, ms: u64, f: ~fn()) { - let mut timer = TimerWatcher::new(self.uvio.uv_loop()); - do timer.start(ms, 0) |timer, status| { - assert!(status.is_none()); - timer.close(||()); - f(); - } - } - fn remote_callback(&mut self, f: ~fn()) -> ~RemoteCallback { ~UvRemoteCallback::new(self.uvio.uv_loop(), f) as ~RemoteCallback } -- cgit 1.4.1-3-g733a5