Skip to content

Commit

Permalink
move field
Browse files Browse the repository at this point in the history
  • Loading branch information
carllerche committed Aug 24, 2022
1 parent 9c7d501 commit de51a1d
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 7 deletions.
6 changes: 3 additions & 3 deletions tokio/src/runtime/builder.rs
Expand Up @@ -85,13 +85,13 @@ pub struct Builder {
/// How many ticks before yielding to the driver for timer and I/O events?
pub(super) event_interval: u32,

#[cfg(tokio_unstable)]
pub(super) unhandled_panic: UnhandledPanic,

/// When true, the multi-threade scheduler LIFO slot should not be used.
///
/// This option should only be exposed as unstable.
pub(super) disable_lifo_slot: bool,

#[cfg(tokio_unstable)]
pub(super) unhandled_panic: UnhandledPanic,
}

cfg_unstable! {
Expand Down
8 changes: 4 additions & 4 deletions tokio/src/runtime/config.rs
Expand Up @@ -13,10 +13,6 @@ pub(crate) struct Config {
/// Callback for a worker unparking itself
pub(crate) after_unpark: Option<Callback>,

#[cfg(tokio_unstable)]
/// How to respond to unhandled task panics.
pub(crate) unhandled_panic: crate::runtime::UnhandledPanic,

/// The multi-threaded scheduler includes a per-worker LIFO slot used to
/// store the last scheduled task. This can improve certain usage patterns,
/// especially message passing between tasks. However, this LIFO slot is not
Expand All @@ -25,4 +21,8 @@ pub(crate) struct Config {
/// Eventually, the LIFO slot **will** become stealable, however as a
/// stop-gap, this unstable option lets users disable the LIFO task.
pub(crate) disable_lifo_slot: bool,

#[cfg(tokio_unstable)]
/// How to respond to unhandled task panics.
pub(crate) unhandled_panic: crate::runtime::UnhandledPanic,
}

0 comments on commit de51a1d

Please sign in to comment.