extern/nushell
1
0
Fork 1
mirror of https://github.com/nushell/nushell.git synced 2024-10-18 00:04:34 +02:00
Code Issues Packages Projects Releases Wiki Activity
0a9897c5ca
nushell/src/lib.rs

38 lines
1007 B
Rust
Raw Normal View History

Restructuring
2019-08-02 21:15:07 +02:00
#![feature(generators)]
#![feature(proc_macro_hygiene)]
WIP improve error infrastructure Also simplify commands and reduce papercuts
2019-07-03 22:31:15 +02:00
#[macro_use]
mod prelude;
First working plugin
2019-06-27 06:56:48 +02:00
mod cli;
mod commands;
mod context;
mod env;
mod errors;
mod evaluate;
mod format;
mod git;
mod object;
mod parser;
Add filter and sink plugins
2019-07-02 09:56:20 +02:00
mod plugin;
First working plugin
2019-06-27 06:56:48 +02:00
mod shell;
mod stream;
Tests pass!
2019-07-24 00:22:11 +02:00
mod traits;
Clean up lint errors
2019-07-24 06:10:48 +02:00
mod utils;
First working plugin
2019-06-27 06:56:48 +02:00
Introduce CallInfo, which abstracts args, name_span, and source_map
2019-07-20 04:27:10 +02:00
pub use crate::commands::command::{CallInfo, ReturnSuccess, ReturnValue};
Move textview to plugin
2019-07-24 19:14:30 +02:00
pub use crate::context::{SourceMap, SpanSource};
Add binary type and tree sink
2019-07-04 07:11:56 +02:00
pub use crate::env::host::BasicHost;
Add support for ~ expansion This ended up being a bit of a yak shave. The basic idea in this commit is to expand `~` in paths, but only in paths. The way this is accomplished is by doing the expansion inside of the code that parses literal syntax for `SyntaxType::Path`. As a quick refresher: every command is entitled to expand its arguments in a custom way. While this could in theory be used for general-purpose macros, today the expansion facility is limited to syntactic hints. For example, the syntax `where cpu > 0` expands under the hood to `where { $it.cpu > 0 }`. This happens because the first argument to `where` is defined as a `SyntaxType::Block`, and the parser coerces binary expressions whose left-hand-side looks like a member into a block when the command is expecting one. This is mildly more magical than what most programming languages would do, but we believe that it makes sense to allow commands to fine-tune the syntax because of the domain nushell is in (command-line shells). The syntactic expansions supported by this facility are relatively limited. For example, we don't allow `$it` to become a bare word, simply because the command asks for a string in the relevant position. That would quickly become more confusing than it's worth. This PR adds a new `SyntaxType` rule: `SyntaxType::Path`. When a command declares a parameter as a `SyntaxType::Path`, string literals and bare words passed as an argument to that parameter are processed using the path expansion rules. Right now, that only means that `~` is expanded into the home directory, but additional rules are possible in the future. By restricting this expansion to a syntactic expansion when passed as an argument to a command expecting a path, we avoid making `~` a generally reserved character. This will also allow us to give good tab completion for paths with `~` characters in them when a command is expecting a path. In order to accomplish the above, this commit changes the parsing functions to take a `Context` instead of just a `CommandRegistry`. From the perspective of macro expansion, you can think of the `CommandRegistry` as a dictionary of in-scope macros, and the `Context` as the compile-time state used in expansion. This could gain additional functionality over time as we find more uses for the expansion system.
2019-08-26 21:21:03 +02:00
pub use crate::parser::hir::SyntaxType;
Remove unused code Closes #467
2019-09-02 08:11:05 +02:00
pub use crate::parser::parse::token_tree_builder::TokenTreeBuilder;
Add filter and sink plugins
2019-07-02 09:56:20 +02:00
pub use crate::plugin::{serve_plugin, Plugin};
Remove unwraps and clean up playground The original intent of this patch was to remove more unwraps to reduce panics. I then lost a ton of time to the fact that the playground isn't in a temp directory (because of permissions issues on Windows). This commit improves the test facilities to: - use a tempdir for the playground - change the playground API so you instantiate it with a block that encloses the lifetime of the tempdir - the block is called with a `dirs` argument that has `dirs.test()` and other important directories that we were computing by hand all the time - the block is also called with a `playground` argument that you can use to construct files (it's the same `Playground` as before) - change the nu! and nu_error! macros to produce output instead of taking a variable binding - change the nu! and nu_error! macros to do the cwd() transformation internally - change the nu! and nu_error! macros to take varargs at the end that get interpolated into the running command I didn't manage to finish porting all of the tests, so a bunch of tests are currently commented out. That will need to change before we land this patch.
2019-08-28 19:01:16 +02:00
pub use crate::utils::{AbsoluteFile, AbsolutePath, RelativePath};
First working plugin
2019-06-27 06:56:48 +02:00
pub use cli::cli;
Migrated numerics to BigInt/BigDecimal This commit migrates Value's numeric types to BigInt and BigDecimal. The basic idea is that overflow errors aren't great in a shell environment, and not really necessary. The main immediate consequence is that new errors can occur when serializing Nu values to other formats. You can see this in changes to the various serialization formats (JSON, TOML, etc.). There's a new `CoerceInto` trait that uses the `ToPrimitive` trait from `num_traits` to attempt to coerce a `BigNum` or `BigDecimal` into a target type, and produces a `RangeError` (kind of `ShellError`) if the coercion fails. Another possible future consequence is that certain performance-critical numeric operations might be too slow. If that happens, we can introduce specialized numeric types to help improve the performance of those situations, based on the real-world experience.
2019-09-01 18:20:31 +02:00
pub use errors::{CoerceInto, ShellError};
Basic support for decimal numbers This commit is more substantial than it looks: there was basically no real support for decimals before, and that impacted values all the way through. I also made Size contain a decimal instead of an integer (`1.6kb` is a reasonable thing to type), which impacted a bunch of code. The biggest impact of this commit is that it creates many more possible ways for valid nu types to fail to serialize as toml, json, etc. which typically can't support the full range of Decimal (or Bigint, which I also think we should support). This commit makes to-toml fallible, and a similar effort is necessary for the rest of the serializations. We also need to figure out how to clearly communicate to users what has happened, but failing to serialize to toml seems clearly superior to me than weird errors in basic math operations.
2019-08-30 19:29:04 +02:00
pub use num_traits::cast::ToPrimitive;
First working plugin
2019-06-27 06:56:48 +02:00
pub use object::base::{Primitive, Value};
initial change to Tagged<Value>
2019-08-01 03:58:42 +02:00
pub use object::dict::{Dictionary, TaggedDictBuilder};
pub use object::meta::{Span, Tag, Tagged, TaggedItem};
First working plugin
2019-06-27 06:56:48 +02:00
pub use parser::parse::text::Text;
Restructuring
2019-08-02 21:15:07 +02:00
pub use parser::registry::{EvaluatedArgs, NamedType, PositionalType, Signature};
Reference in New Issue Copy Permalink