From 8308518739b503321509ee9a6a621ae2caddee4e Mon Sep 17 00:00:00 2001 From: Jim Infield Date: Sat, 17 Jul 2021 21:32:06 -0500 Subject: [PATCH] Initial commit --- .exercism/metadata.json | 1 + .gitignore | 8 +++ Cargo.toml | 4 ++ README.md | 85 +++++++++++++++++++++++++++ src/lib.rs | 23 ++++++++ tests/matching-brackets.rs | 116 +++++++++++++++++++++++++++++++++++++ 6 files changed, 237 insertions(+) create mode 100644 .exercism/metadata.json create mode 100644 .gitignore create mode 100644 Cargo.toml create mode 100644 README.md create mode 100644 src/lib.rs create mode 100644 tests/matching-brackets.rs diff --git a/.exercism/metadata.json b/.exercism/metadata.json new file mode 100644 index 0000000..996d04a --- /dev/null +++ b/.exercism/metadata.json @@ -0,0 +1 @@ +{"track":"rust","exercise":"matching-brackets","id":"b82aef77a6a34749a8715a01ca1b4cf8","url":"https://exercism.io/my/solutions/b82aef77a6a34749a8715a01ca1b4cf8","handle":"jinfield","is_requester":true,"auto_approve":false} \ No newline at end of file diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..db7f315 --- /dev/null +++ b/.gitignore @@ -0,0 +1,8 @@ +# Generated by Cargo +# will have compiled files and executables +/target/ +**/*.rs.bk + +# Remove Cargo.lock from gitignore if creating an executable, leave it for libraries +# More information here http://doc.crates.io/guide.html#cargotoml-vs-cargolock +Cargo.lock diff --git a/Cargo.toml b/Cargo.toml new file mode 100644 index 0000000..2e7dafa --- /dev/null +++ b/Cargo.toml @@ -0,0 +1,4 @@ +[package] +edition = "2018" +name = "matching-brackets" +version = "2.0.0" diff --git a/README.md b/README.md new file mode 100644 index 0000000..9d80e21 --- /dev/null +++ b/README.md @@ -0,0 +1,85 @@ +# Matching Brackets + +Given a string containing brackets `[]`, braces `{}`, parentheses `()`, +or any combination thereof, verify that any and all pairs are matched +and nested correctly. + +## 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/main/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 + +Ginna Baker + +## Submitting Incomplete Solutions +It's possible to submit an incomplete solution so you can see how others have completed the exercise. diff --git a/src/lib.rs b/src/lib.rs new file mode 100644 index 0000000..c818158 --- /dev/null +++ b/src/lib.rs @@ -0,0 +1,23 @@ +pub fn brackets_are_balanced(string: &str) -> bool { + use std::collections::HashMap; + + let pairs: HashMap = [(')', '('), ('}', '{'), (']', '[')] + .iter().cloned().collect(); + + let mut stack = vec![]; + + for char in string.chars() { + match char { + '(' | '{' | '[' => stack.push(char), + ')' | '}' | ']' => { + if let Some(left) = stack.pop() { + if let Some(right) = pairs.get(&char) { + if left != *right { return false } + } + } else { return false } + }, + _ => {}, + } + } + stack.is_empty() +} \ No newline at end of file diff --git a/tests/matching-brackets.rs b/tests/matching-brackets.rs new file mode 100644 index 0000000..8d82949 --- /dev/null +++ b/tests/matching-brackets.rs @@ -0,0 +1,116 @@ +use matching_brackets::brackets_are_balanced; + +#[test] +fn paired_square_brackets() { + assert!(brackets_are_balanced("[]")); +} + +#[test] +//#[ignore] +fn empty_string() { + assert!(brackets_are_balanced("")); +} + +#[test] +//#[ignore] +fn unpaired_brackets() { + assert!(!brackets_are_balanced("[[")); +} + +#[test] +//#[ignore] +fn wrong_ordered_brackets() { + assert!(!brackets_are_balanced("}{")); +} + +#[test] +//#[ignore] +fn wrong_closing_bracket() { + assert!(!brackets_are_balanced("{]")); +} + +#[test] +//#[ignore] +fn paired_with_whitespace() { + assert!(brackets_are_balanced("{ }")); +} + +#[test] +//#[ignore] +fn partially_paired_brackets() { + assert!(!brackets_are_balanced("{[])")); +} + +#[test] +//#[ignore] +fn simple_nested_brackets() { + assert!(brackets_are_balanced("{[]}")); +} + +#[test] +//#[ignore] +fn several_paired_brackets() { + assert!(brackets_are_balanced("{}[]")); +} + +#[test] +//#[ignore] +fn paired_and_nested_brackets() { + assert!(brackets_are_balanced("([{}({}[])])")); +} + +#[test] +//#[ignore] +fn unopened_closing_brackets() { + assert!(!brackets_are_balanced("{[)][]}")); +} + +#[test] +//#[ignore] +fn unpaired_and_nested_brackets() { + assert!(!brackets_are_balanced("([{])")); +} + +#[test] +//#[ignore] +fn paired_and_wrong_nested_brackets() { + assert!(!brackets_are_balanced("[({]})")); +} + +#[test] +//#[ignore] +fn paired_and_incomplete_brackets() { + assert!(!brackets_are_balanced("{}[")); +} + +#[test] +//#[ignore] +fn too_many_closing_brackets() { + assert!(!brackets_are_balanced("[]]")); +} + +#[test] +//#[ignore] +fn early_incomplete_brackets() { + assert!(!brackets_are_balanced(")()")); +} + +#[test] +//#[ignore] +fn early_mismatched_brackets() { + assert!(!brackets_are_balanced("{)()")); +} + +#[test] +//#[ignore] +fn math_expression() { + assert!(brackets_are_balanced("(((185 + 223.85) * 15) - 543)/2")); +} + +#[test] +//#[ignore] +fn complex_latex_expression() { + let input = "\\left(\\begin{array}{cc} \\frac{1}{3} & x\\\\ \\mathrm{e}^{x} &... x^2 \ + \\end{array}\\right)"; + assert!(brackets_are_balanced(input)); +}