mirror of
https://github.com/fish-shell/fish-shell.git
synced 2024-12-26 12:13:46 +08:00
83fd7ea7c4
This is early work but I guess there's no harm in pushing it?
Some thoughts on the conventions:
Types that live only inside Rust follow Rust naming convention
("FeatureMetadata").
Types that live on both sides of the language boundary follow the existing
naming ("feature_flag_t").
The alternative is to define a type alias ("using feature_flag_t =
rust::FeatureFlag") but that doesn't seem to be supported in "[cxx::bridge]"
blocks. We could put it in a header ("future_feature_flags.h").
"feature_metadata_t" is a variant of "FeatureMetadata" that can cross
the language boundary. This has the advantage that we can avoid tainting
"FeatureMetadata" with "CxxString" and such. This is an experimental approach,
probably not what we should do in general.
27 lines
399 B
Rust
27 lines
399 B
Rust
#![allow(non_camel_case_types)]
|
|
#![allow(dead_code)]
|
|
#![allow(non_upper_case_globals)]
|
|
#![allow(clippy::needless_return)]
|
|
|
|
#[macro_use]
|
|
extern crate lazy_static;
|
|
|
|
mod fd_readable_set;
|
|
mod fds;
|
|
mod ffi;
|
|
mod ffi_init;
|
|
mod ffi_tests;
|
|
mod flog;
|
|
mod future_feature_flags;
|
|
mod signal;
|
|
mod smoke;
|
|
mod topic_monitor;
|
|
mod util;
|
|
mod wchar;
|
|
mod wchar_ext;
|
|
mod wchar_ffi;
|
|
mod wgetopt;
|
|
mod wutil;
|
|
|
|
mod builtins;
|