Move Rust exercises in a subdirectory

1 files changed, 0 insertions, 137 deletions

diff --git a/simple-linked-list/README.md b/simple-linked-list/README.md
deleted file mode 100644
index 47178e8..0000000
--- a/simple-linked-list/README.md
+++ /dev/null
@@ -1,137 +0,0 @@
-# Simple Linked List
-
-Write a simple linked list implementation that uses Elements and a List.
-
-The linked list is a fundamental data structure in computer science,
-often used in the implementation of other data structures. They're
-pervasive in functional programming languages, such as Clojure, Erlang,
-or Haskell, but far less common in imperative languages such as Ruby or
-Python.
-
-The simplest kind of linked list is a singly linked list. Each element in the
-list contains data and a "next" field pointing to the next element in the list
-of elements.
-
-This variant of linked lists is often used to represent sequences or
-push-down stacks (also called a LIFO stack; Last In, First Out).
-
-As a first take, lets create a singly linked list to contain the range (1..10),
-and provide functions to reverse a linked list and convert to and from arrays.
-
-When implementing this in a language with built-in linked lists,
-implement your own abstract data type.
-
-## Implementation Hints
-
-Do not implement the struct `SimpleLinkedList` as a wrapper around a `Vec`. Instead, allocate nodes on the heap.  
-This might be implemented as:
-```
-pub struct SimpleLinkedList<T> {
-    head: Option<Box<Node<T>>>,
-}
-```
-The `head` field points to the first element (Node) of this linked list.  
-This implementation also requires a struct `Node` with the following fields:
-```
-struct Node<T> {
-    data: T,
-    next: Option<Box<Node<T>>>,
-}
-```
-`data` contains the stored data, and `next` points to the following node (if available) or None.  
-
-### Why `Option<Box<Node<T>>>` and not just `Option<Node<T>>`?
-Try it on your own. You will get the following error.
-
-```
-| struct Node<T>
-| ^^^^^^^^^^^^^^ recursive type has infinite size
-...
-|     next: Option<Node<T>>,
-|     --------------------- recursive without indirection
- ```
-
- The problem is that at compile time the size of next must be known.
- Since `next` is recursive ("a node has a node has a node..."), the compiler does not know how much memory is to be allocated.
- In contrast, [Box](https://doc.rust-lang.org/std/boxed/) is a heap pointer with a defined size.
-
-
-## Rust Installation
-
-Refer to the [exercism help page][help-page] for Rust installation and learning
-resources.
-
-## Writing the Code
-
-Execute the tests with:
-
-```bash
-$ cargo test
-```
-
-All but the first test have been ignored. After you get the first test to
-pass, open the tests source file which is located in the `tests` directory
-and remove the `#[ignore]` flag from the next test and get the tests to pass
-again. Each separate test is a function with `#[test]` flag above it.
-Continue, until you pass every test.
-
-If you wish to run all ignored tests without editing the tests source file, use:
-
-```bash
-$ cargo test -- --ignored
-```
-
-To run a specific test, for example `some_test`, you can use:
-
-```bash
-$ cargo test some_test
-```
-
-If the specific test is ignored use:
-
-```bash
-$ cargo test some_test -- --ignored
-```
-
-To learn more about Rust tests refer to the [online test documentation][rust-tests]
-
-Make sure to read the [Modules][modules] chapter if you
-haven't already, it will help you with organizing your files.
-
-## Further improvements
-
-After you have solved the exercise, please consider using the additional utilities, described in the [installation guide](https://exercism.io/tracks/rust/installation), to further refine your final solution.
-
-To format your solution, inside the solution directory use
-
-```bash
-cargo fmt
-```
-
-To see, if your solution contains some common ineffective use cases, inside the solution directory use
-
-```bash
-cargo clippy --all-targets
-```
-
-## Submitting the solution
-
-Generally you should submit all files in which you implemented your solution (`src/lib.rs` in most cases). If you are using any external crates, please consider submitting the `Cargo.toml` file. This will make the review process faster and clearer.
-
-## Feedback, Issues, Pull Requests
-
-The [exercism/rust](https://github.com/exercism/rust) repository on GitHub is the home for all of the Rust exercises. If you have feedback about an exercise, or want to help implement new exercises, head over there and create an issue. Members of the rust track team are happy to help!
-
-If you want to know more about Exercism, take a look at the [contribution guide](https://github.com/exercism/docs/blob/master/contributing-to-language-tracks/README.md).
-
-[help-page]: https://exercism.io/tracks/rust/learning
-[modules]: https://doc.rust-lang.org/book/ch07-02-defining-modules-to-control-scope-and-privacy.html
-[cargo]: https://doc.rust-lang.org/book/ch14-00-more-about-cargo.html
-[rust-tests]: https://doc.rust-lang.org/book/ch11-02-running-tests.html
-
-## Source
-
-Inspired by 'Data Structures and Algorithms with Object-Oriented Design Patterns in Ruby', singly linked-lists. [https://web.archive.org/web/20160731005714/http://brpreiss.com/books/opus8/html/page96.html](https://web.archive.org/web/20160731005714/http://brpreiss.com/books/opus8/html/page96.html)
-
-## Submitting Incomplete Solutions
-It's possible to submit an incomplete solution so you can see how others have completed the exercise.