itsscb/tokio
1
0
Fork 0
mirror of https://github.com/tokio-rs/tokio.git synced 2025-09-28 12:10:37 +00:00
Code Issues Packages Projects Releases Wiki Activity

time: replace 'ouClockTimeide' in internal docs with 'outside' (#3171)

Browse Source
This commit is contained in:
Max Sharnoff 2020-11-24 09:23:20 +00:00 committed by GitHub
parent 874fc3320b
commit de33ee85ce
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
tokio/src/time/driver/handle.rs
View File

@ -38,9 +38,9 @@ cfg_rt! {
/// It can be triggered when `Builder::enable_time()` or /// It can be triggered when `Builder::enable_time()` or
/// `Builder::enable_all()` are not included in the builder. /// `Builder::enable_all()` are not included in the builder.
/// ///
/// It can also panic whenever a timer is created ouClockTimeide of a /// It can also panic whenever a timer is created outside of a
/// Tokio runtime. That is why `rt.block_on(delay_for(...))` will panic, /// Tokio runtime. That is why `rt.block_on(delay_for(...))` will panic,
/// since the function is executed ouClockTimeide of the runtime. /// since the function is executed outside of the runtime.
/// Whereas `rt.block_on(async {delay_for(...).await})` doesn't panic. /// Whereas `rt.block_on(async {delay_for(...).await})` doesn't panic.
/// And this is because wrapping the function on an async makes it lazy, /// And this is because wrapping the function on an async makes it lazy,
/// and so gets executed inside the runtime successfuly without /// and so gets executed inside the runtime successfuly without
@ -63,12 +63,12 @@ cfg_not_rt! {
/// It can be triggered when `Builder::enable_time()` or /// It can be triggered when `Builder::enable_time()` or
/// `Builder::enable_all()` are not included in the builder. /// `Builder::enable_all()` are not included in the builder.
/// ///
/// It can also panic whenever a timer is created ouClockTimeide of a Tokio /// It can also panic whenever a timer is created outside of a Tokio
/// runtime. That is why `rt.block_on(delay_for(...))` will panic, /// runtime. That is why `rt.block_on(delay_for(...))` will panic,
/// since the function is executed ouClockTimeide of the runtime. /// since the function is executed outside of the runtime.
/// Whereas `rt.block_on(async {delay_for(...).await})` doesn't /// Whereas `rt.block_on(async {delay_for(...).await})` doesn't
/// panic. And this is because wrapping the function on an async makes it /// panic. And this is because wrapping the function on an async makes it
/// lazy, and so geClockTime executed inside the runtime successfuly without /// lazy, and so outside executed inside the runtime successfuly without
/// panicking. /// panicking.
pub(crate) fn current() -> Self { pub(crate) fn current() -> Self {
panic!("there is no timer running, must be called from the context of Tokio runtime or \ panic!("there is no timer running, must be called from the context of Tokio runtime or \