Extract core stuff into own crates
This commit extracts five new crates:
- nu-source, which contains the core source-code handling logic in Nu,
including Text, Span, and also the pretty.rs-based debug logic
- nu-parser, which is the parser and expander logic
- nu-protocol, which is the bulk of the types and basic conveniences
used by plugins
- nu-errors, which contains ShellError, ParseError and error handling
conveniences
- nu-textview, which is the textview plugin extracted into a crate
One of the major consequences of this refactor is that it's no longer
possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so
a lot of types became more concrete (Value became a concrete type
instead of Spanned<Value>, for example).
This also turned a number of inherent methods in the main nu crate into
plain functions (impl Value {} became a bunch of functions in the
`value` namespace in `crate::data::value`).
2019-11-26 03:30:48 +01:00
|
|
|
#[macro_use]
|
|
|
|
|
mod macros;
|
|
|
|
|
|
|
|
|
|
mod call_info;
|
|
|
|
|
mod maybe_owned;
|
|
|
|
|
mod plugin;
|
|
|
|
|
mod return_value;
|
|
|
|
|
mod signature;
|
|
|
|
|
mod syntax_shape;
|
|
|
|
|
mod type_name;
|
|
|
|
|
mod value;
|
|
|
|
|
|
|
|
|
|
pub use crate::call_info::{CallInfo, EvaluatedArgs};
|
|
|
|
|
pub use crate::maybe_owned::MaybeOwned;
|
|
|
|
|
pub use crate::plugin::{serve_plugin, Plugin};
|
|
|
|
|
pub use crate::return_value::{CommandAction, ReturnSuccess, ReturnValue};
|
|
|
|
|
pub use crate::signature::{NamedType, PositionalType, Signature};
|
|
|
|
|
pub use crate::syntax_shape::SyntaxShape;
|
|
|
|
|
pub use crate::type_name::{PrettyType, ShellTypeName, SpannedTypeName};
|
2019-12-09 19:39:51 +01:00
|
|
|
pub use crate::value::column_path::{did_you_mean, ColumnPath, PathMember, UnspannedPathMember};
|
2019-12-04 20:52:31 +01:00
|
|
|
pub use crate::value::dict::{Dictionary, TaggedDictBuilder};
|
Extract core stuff into own crates
This commit extracts five new crates:
- nu-source, which contains the core source-code handling logic in Nu,
including Text, Span, and also the pretty.rs-based debug logic
- nu-parser, which is the parser and expander logic
- nu-protocol, which is the bulk of the types and basic conveniences
used by plugins
- nu-errors, which contains ShellError, ParseError and error handling
conveniences
- nu-textview, which is the textview plugin extracted into a crate
One of the major consequences of this refactor is that it's no longer
possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so
a lot of types became more concrete (Value became a concrete type
instead of Spanned<Value>, for example).
This also turned a number of inherent methods in the main nu crate into
plain functions (impl Value {} became a bunch of functions in the
`value` namespace in `crate::data::value`).
2019-11-26 03:30:48 +01:00
|
|
|
pub use crate::value::evaluate::{Evaluate, EvaluateTrait, Scope};
|
2019-12-09 19:39:51 +01:00
|
|
|
pub use crate::value::primitive::format_primitive;
|
Extract core stuff into own crates
This commit extracts five new crates:
- nu-source, which contains the core source-code handling logic in Nu,
including Text, Span, and also the pretty.rs-based debug logic
- nu-parser, which is the parser and expander logic
- nu-protocol, which is the bulk of the types and basic conveniences
used by plugins
- nu-errors, which contains ShellError, ParseError and error handling
conveniences
- nu-textview, which is the textview plugin extracted into a crate
One of the major consequences of this refactor is that it's no longer
possible to `impl X for Spanned<Y>` outside of the `nu-source` crate, so
a lot of types became more concrete (Value became a concrete type
instead of Spanned<Value>, for example).
This also turned a number of inherent methods in the main nu crate into
plain functions (impl Value {} became a bunch of functions in the
`value` namespace in `crate::data::value`).
2019-11-26 03:30:48 +01:00
|
|
|
pub use crate::value::primitive::Primitive;
|
|
|
|
|
pub use crate::value::{UntaggedValue, Value};
|
