base on An embedded scheme interpreter in Rust # Steel <div align="center"> <img width="150px" src="images/styled.png"> </div> <div align="center"> An embeddable and extensible scheme dialect built in Rust. ![Actions Status](https://github.com/mattwparas/steel/workflows/Build/badge.svg) ![Actions Status](https://github.com/mattwparas/steel/workflows/Docker%20CI/badge.svg) [![Coverage Status](https://coveralls.io/repos/github/mattwparas/steel/badge.svg?branch=master)](https://coveralls.io/github/mattwparas/steel?branch=master) [![Discord Chat](https://img.shields.io/discord/1152443024715034675.svg?logo=discord&label=discord)](https://discord.gg/WwFRXdN6HU) [![Matrix Chat](https://img.shields.io/matrix/steel:matrix.org?logo=element&label=matrix)](https://matrix.to/#/#steel:matrix.org) <a href="https://mattwparas.github.io/steel-playground/"> <b>Try it on the Playground</b> </a> · <a href="https://mattwparas.github.io/steel/book"> <b>Read the Steel book (WIP)</b> </a> </div> ## About `Steel` is an embeddable scheme interpreter, with a standalone interpreter/REPL included as well. The language is implemented as a bytecode virtual machine. At the moment, it is mostly compliant with R5RS, only missing `let-syntax` support. Support for R7Rs is underway. > **Warning** > The API is relatively stable, however it may change at any time while pre 1.0. > Care will be taken to keep things backwards compatible where possible. ## Features - [R5RS](https://standards.scheme.org/official/r5rs.pdf) support - Modules, using `require` and `provide` much like Racket. - `syntax-rules` and `syntax-case` macros. - Easy integration with native Rust functions and structs, either through embedding or via FFI. - Higher order Contracts - Built in immutable data structures, including: - lists - vectors - hashmaps - hashsets For more details, see the [book](https://mattwparas.github.io/steel/book). ## Getting Started This github repository contains a CLI interpreter. To try it out on the online playground, go to the [Steel playground](https://mattwparas.github.io/steel-playground/). To get started using a REPL with the crates, make sure you first have Rust installed. Then, clone the repo and run the following command: ```bash cargo run ``` This will launch a REPL instance that looks something like this: <p align="center"> <img src="images/steel.gif" width="100%"> </p> ### Full install If you'd like to install everything, just run the following command: ```bash cargo xtask install ``` This will install: - The steel interpreter, `steel` - The package manager, `forge` - The dylib installer, `cargo-steel-lib` (also available via the interpreter) - The steel language server - The standard library, found under the `cogs` directory #### Nix Steel can also be installed with Nix. Add the following to your Home Manager config: ```nix home.packages = [ pkgs.steel ]; ``` ### Packages If you would like to customize the location of installed packages, please set the `STEEL_HOME` environment variable. Steel currently follows XDG if present, and otherwise assumes the default of `$HOME/.steel` if the `STEEL_HOME` environment variable is not already set. ## License Licensed under either of - Apache License, Version 2.0 ([LICENSE-APACHE](LICENSE-APACHE) or http://www.apache.org/licenses/LICENSE-2.0) - MIT license ([LICENSE-MIT](LICENSE-MIT) or http://opensource.org/licenses/MIT) at your option. ## Contribution Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions. See [CONTRIBUTING.md](./CONTRIBUTING.md). ", Assign "at most 3 tags" to the expected json: {"id":"5611","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"