diff options
| author | srdusr <[email protected]> | 2024-08-03 20:07:00 +0200 |
|---|---|---|
| committer | srdusr <[email protected]> | 2024-08-03 20:07:00 +0200 |
| commit | 35a28a257644483495ac2bd6a5fb1e109e8c1f26 (patch) | |
| tree | 37944a7a2a61bf7ff977fa6349742d1a53ed5ad3 /crates/platform/src | |
| parent | f166df4d979162ae09b439c87cdc64f2b0981308 (diff) | |
| download | srdwm-35a28a257644483495ac2bd6a5fb1e109e8c1f26.tar.gz srdwm-35a28a257644483495ac2bd6a5fb1e109e8c1f26.zip | |
Fix doc-comment file references left stale by today's six module splits
~17 comments across the codebase still pointed at udev.rs/winit.rs/
state.rs by their old flat-file names after those became udev/,
winit/, state/ directories - found while auditing what this work
rushed, since the split verification (function/struct-name diffing,
full test suite) checked structural correctness but never comment
accuracy. Updated each to either the specific new file (e.g. "see
state.rs's REPEAT_DELAY" -> "see state/mod.rs's REPEAT_DELAY",
"udev.rs's monitors()" -> "udev/platform.rs's monitors()") or the bare
module name where the reference was already generic ("the udev/winit
backends", not a specific location).
Diffstat (limited to 'crates/platform/src')
| -rw-r--r-- | crates/platform/src/ipc.rs | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/crates/platform/src/ipc.rs b/crates/platform/src/ipc.rs index 0d2396a..a366138 100644 --- a/crates/platform/src/ipc.rs +++ b/crates/platform/src/ipc.rs @@ -4,9 +4,9 @@ //! `crates/ctl` (the `srd` binary) is the reference client. //! //! Deliberately synchronous and non-blocking-polled from each backend's -//! `poll_events()` tick (see `udev.rs`/`winit.rs`), the same way the +//! `poll_events()` tick (see `udev`/`winit`), the same way the //! Wayland client socket itself is accepted - there is no calloop event -//! loop shared by both backends (`winit.rs` has none at all), so this +//! loop shared by both backends (`winit` has none at all), so this //! avoids needing two different registration mechanisms for one feature. //! An ordinary request is one request/one response/close; nothing here is //! held open for those, so a stalled or hostile client can only ever leak |