Antoine Stevan 05f1b41275
remove match from the standard library (#8625)
Should close #8616.
Related to #8590.

# Description
With the new builtin `match` command introduced in the `rust` source in
#8590, there is no need to have a custom `match` in the standard
library.
This PR removes the `match` command from `std.nu` and the associated
test.

# User-Facing Changes
Users can not access `match` from `std.nu`.

# Tests + Formatting
```
nu crates/nu-utils/standard_library/tests.nu  --path crates/nu-utils/standard_library/ out+err> /dev/null; ($env.LAST_EXIT_CODE == 0)
```
gives `true`

# After Submitting
```
$nothing
```
2023-03-26 10:57:41 +02:00
..
2023-03-17 21:29:15 +13:00
2023-03-17 21:29:15 +13:00
2023-03-17 21:29:15 +13:00
2023-03-17 21:29:15 +13:00
2023-03-17 21:29:15 +13:00
2023-03-17 21:29:15 +13:00
2023-03-17 21:29:15 +13:00
2023-03-17 21:29:15 +13:00
2023-03-17 21:29:15 +13:00
2023-03-17 21:29:15 +13:00
2023-03-17 21:29:15 +13:00
2023-03-17 21:29:15 +13:00
2023-03-17 21:29:15 +13:00
2022-02-07 14:54:06 -05:00

Nushell core libraries and plugins

These sub-crates form both the foundation for Nu and a set of plugins which extend Nu with additional functionality.

Foundational libraries are split into two kinds of crates:

  • Core crates - those crates that work together to build the Nushell language engine
  • Support crates - a set of crates that support the engine with additional features like JSON support, ANSI support, and more.

Plugins are likewise also split into two types:

  • Core plugins - plugins that provide part of the default experience of Nu, including access to the system properties, processes, and web-connectivity features.
  • Extra plugins - these plugins run a wide range of different capabilities like working with different file types, charting, viewing binary data, and more.