fish-shell/src/builtins/mod.rs

65 lines
1.1 KiB
Rust
Raw Normal View History

pub mod shared;
2023-02-06 05:08:32 +08:00
pub mod abbr;
2023-06-17 05:38:08 +08:00
pub mod argparse;
pub mod bg;
pub mod bind;
pub mod block;
pub mod builtin;
pub mod cd;
pub mod command;
pub mod commandline;
pub mod complete;
pub mod contains;
pub mod count;
pub mod disown;
2023-02-06 05:08:32 +08:00
pub mod echo;
2023-02-11 01:19:22 +08:00
pub mod emit;
pub mod eval;
Port fd_monitor (and its needed components) I needed to rename some types already ported to rust so they don't clash with their still-extant cpp counterparts. Helper ffi functions added to avoid needing to dynamically allocate an FdMonitorItem for every fd (we use dozens per basic prompt). I ported some functions from cpp to rust that are used only in the backend but without removing their existing cpp counterparts so cpp code can continue to use their version of them (`wperror` and `make_detached_pthread`). I ran into issues porting line-by-line logic because rust inverts the behavior of `std::remove_if(..)` by making it (basically) `Vec::retain_if(..)` so I replaced bools with an explict enum to make everything clearer. I'll port the cpp tests for this separately, for now they're using ffi. Porting closures was ugly. It's nothing hard, but it's very ugly as now each capturing lambda has been changed into an explicit struct that contains its parameters (that needs to be dynamically allocated), a standalone callback (member) function to replace the lambda contents, and a separate trampoline function to call it from rust over the shared C abi (not really relevant to x86_64 w/ its single calling convention but probably needed on other platforms). I don't like that `fd_monitor.rs` has its own `c_void`. I couldn't find a way to move that to `ffi.rs` but still get cxx bridge to consider it a shared POD. Every time I moved it to a different module, it would consider it to be an opaque rust type instead. I worry this means we're going to have multiple `c_void1`, `c_void2`, etc. types as we continue to port code to use function pointers. Also, rust treats raw pointers as foreign so you can't do `impl Send for * const Foo` even if `Foo` is from the same module. That necessitated a wrapper type (`void_ptr`) that implements `Send` and `Sync` so we can move stuff between threads. The code in fd_monitor_t has been split into two objects, one that is used by the caller and a separate one associated with the background thread (this is made nice and clean by rust's ownership model). Objects not needed under the lock (i.e. accessed by the background thread exclusively) were moved to the separate `BackgroundFdMonitor` type.
2023-02-18 09:21:44 +08:00
pub mod exit;
pub mod fg;
pub mod function;
2023-08-09 02:12:05 +08:00
pub mod functions;
pub mod history;
pub mod jobs;
pub mod math;
2023-07-29 19:28:02 +08:00
pub mod path;
pub mod printf;
pub mod pwd;
2023-02-19 05:06:05 +08:00
pub mod random;
pub mod read;
2023-03-06 10:38:41 +08:00
pub mod realpath;
2023-02-19 00:13:58 +08:00
pub mod r#return;
pub mod set;
pub mod set_color;
pub mod source;
pub mod status;
pub mod string;
pub mod test;
2023-02-25 04:14:13 +08:00
pub mod r#type;
pub mod ulimit;
pub mod wait;
#[cfg(test)]
mod tests;
mod prelude {
pub use super::shared::*;
pub use libc::c_int;
pub use std::borrow::Cow;
#[allow(unused_imports)]
pub(crate) use crate::{
flog::{FLOG, FLOGF},
io::{IoStreams, SeparationType},
parser::Parser,
wchar::prelude::*,
wgetopt::{
wopt,
ArgType::{self, *},
WGetopter, WOption, NON_OPTION_CHAR,
},
wutil::{fish_wcstoi, fish_wcstol, fish_wcstoul},
};
}