Remove SystemExt trait

README.md

@@ -16,7 +16,7 @@ It currently supports the following OSes (alphabetically sorted):
 
 You can still use `sysinfo` on non-supported OSes, it'll simply do nothing and always return
 empty values. You can check in your program directly if an OS is supported by checking the
-[`SystemExt::IS_SUPPORTED`] constant.
+[`IS_SUPPORTED`] constant.
 
 The minimum-supported version of `rustc` is **1.63**.
 
@@ -36,7 +36,7 @@ Otherwise, here is a little code sample:
 ```rust
 use sysinfo::{
     Components, ComponentsExt, Disks, NetworkExt, Networks,
-    NetworksExt, ProcessExt, System, SystemExt,
+    NetworksExt, ProcessExt, System,
 };
 
 // Please note that we use "new_all" to ensure that all list of
@@ -100,7 +100,7 @@ Please remember that to have some up-to-date information, you need to call the e
 `refresh` method. For example, for the CPU usage:
 
 ```rust,no_run
-use sysinfo::{CpuExt, System, SystemExt};
+use sysinfo::{CpuExt, System};
 
 let mut sys = System::new();
 
@@ -111,7 +111,7 @@ loop {
     }
     // Sleeping to let time for the system to run for long
     // enough to have useful information.
-    std::thread::sleep(System::MINIMUM_CPU_UPDATE_INTERVAL);
+    std::thread::sleep(sysinfo::MINIMUM_CPU_UPDATE_INTERVAL);
 }
 ```
 

benches/basic.rs

@@ -3,7 +3,7 @@
 extern crate test;
 
 use sysinfo::get_current_pid;
-use sysinfo::{ComponentsExt, NetworksExt, SystemExt, UsersExt};
+use sysinfo::{ComponentsExt, NetworksExt, UsersExt};
 
 #[bench]
 fn bench_new(b: &mut test::Bencher) {

examples/simple.rs

@@ -9,7 +9,7 @@ use std::str::FromStr;
 use sysinfo::Signal::*;
 use sysinfo::{
     Components, ComponentsExt, CpuExt, Disks, NetworkExt, Networks, NetworksExt, Pid, ProcessExt,
-    Signal, System, SystemExt, UserExt, Users, UsersExt,
+    Signal, System, UserExt, Users, UsersExt,
 };
 
 const signals: &[Signal] = &[

md_doc/is_supported.md

@@ -0,0 +1,10 @@
+Returns `true` if this OS is supported. Please refer to the
+[crate-level documentation](index.html) to get the list of supported OSes.
+
+```
+if sysinfo::IS_SUPPORTED {
+    println!("This OS is supported!");
+} else {
+    println!("This OS isn't supported (yet?).");
+}
+```

md_doc/minimum_cpu_update_interval.md

@@ -0,0 +1,8 @@
+This is the minimum interval time used internally by `sysinfo` to refresh the CPU time.
+
+⚠️ This value differs from one OS to another.
+
+Why is this constant even needed?
+
+If refreshed too often, the CPU usage of processes will be `0` whereas on Linux it'll
+always be the maximum value (`number of CPUs * 100`).

md_doc/serde.md

@@ -2,7 +2,7 @@
 With the `serde` feature enabled, you can then serialize `sysinfo` types. Let's see an example with `serde_json`:
 
 ```
-use sysinfo::{System, SystemExt};
+use sysinfo::System;
 
 let mut sys = System::new_all();
 // First we update all information of our `System` struct.

md_doc/supported_signals.md

@@ -0,0 +1,8 @@
+Returns the list of the supported signals on this system (used by
+[`ProcessExt::kill_with`][crate::ProcessExt::kill_with]).
+
+```
+use sysinfo::{System, SUPPORTED_SIGNALS};
+
+println!("supported signals: {:?}", SUPPORTED_SIGNALS);
+```

src/c_interface.rs

@@ -1,8 +1,6 @@
 // Take a look at the license at the top of the repository in the LICENSE file.
 
-use crate::{
-    CpuExt, Disks, NetworkExt, Networks, NetworksExt, Pid, Process, ProcessExt, System, SystemExt,
-};
+use crate::{CpuExt, Disks, NetworkExt, Networks, NetworksExt, Pid, Process, ProcessExt, System};
 use libc::{self, c_char, c_float, c_uint, c_void, size_t};
 use std::borrow::BorrowMut;
 use std::ffi::CString;