migrations/winit
1
0
Fork 0
mirror of https://github.com/rust-windowing/winit.git synced 2026-09-01 06:10:07 -04:00
Code Issues Packages Projects Releases Wiki Activity

Remove old docs about EventLoop::run

Browse Source
This commit is contained in:
Kirill Chibisov
2023-09-22 13:46:52 +04:00
parent 367a2ae057
commit c5cef46060
2 changed files with 1 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/event_loop.rs
View File

@@ -223,8 +223,6 @@ impl<T> EventLoop<T> {
/// ///
/// ## Platform-specific /// ## Platform-specific
/// ///
/// - **X11 / Wayland:** The program terminates with exit code 1 if the display server
/// disconnects.
/// - **iOS:** Will never return to the caller and so values not passed to this function will /// - **iOS:** Will never return to the caller and so values not passed to this function will
/// *not* be dropped before the process exits. /// *not* be dropped before the process exits.
/// - **Web:** Will _act_ as if it never returns to the caller by throwing a Javascript exception /// - **Web:** Will _act_ as if it never returns to the caller by throwing a Javascript exception

3
src/lib.rs
View File

@@ -30,8 +30,7 @@
//! //!
//! You can retrieve events by calling [`EventLoop::run`][event_loop_run]. This function will //! You can retrieve events by calling [`EventLoop::run`][event_loop_run]. This function will
//! dispatch events for every [`Window`] that was created with that particular [`EventLoop`], and //! dispatch events for every [`Window`] that was created with that particular [`EventLoop`], and
//! will run until [`exit()`] is used, at which //! will run until [`exit()`] is used, at which point [`Event`]`::`[`LoopExiting`].
//! point [`Event`]`::`[`LoopExiting`] is emitted and the entire program terminates.
//! //!
//! Winit no longer uses a `EventLoop::poll_events() -> impl Iterator<Event>`-based event loop //! Winit no longer uses a `EventLoop::poll_events() -> impl Iterator<Event>`-based event loop
//! model, since that can't be implemented properly on some platforms (e.g web, iOS) and works poorly on //! model, since that can't be implemented properly on some platforms (e.g web, iOS) and works poorly on