Published at Oct 06 2019
·
0 comments

Instructions

Test suite

Solution

Given two buckets of different size, demonstrate how to measure an exact number of liters by strategically transferring liters of fluid between the buckets.

Since this mathematical problem is fairly subject to interpretation / individual approach, the tests have been written specifically to expect one overarching solution.

To help, the tests provide you with which bucket to fill first. That means, when starting with the larger bucket full, you are NOT allowed at any point to have the smaller bucket full and the larger bucket empty (aka, the opposite starting point); that would defeat the purpose of comparing both approaches!

Your program will take as input:

- the size of bucket one
- the size of bucket two
- the desired number of liters to reach
- which bucket to fill first, either bucket one or bucket two

Your program should determine:

- the total number of "moves" it should take to reach the desired number of liters, including the first fill
- which bucket should end up with the desired number of liters (let's say this is bucket A) - either bucket one or bucket two
- how many liters are left in the other bucket (bucket B)

Note: any time a change is made to either or both buckets counts as one (1) move.

Example: Bucket one can hold up to 7 liters, and bucket two can hold up to 11 liters. Let's say bucket one, at a given step, is holding 7 liters, and bucket two is holding 8 liters (7,8). If you empty bucket one and make no change to bucket two, leaving you with 0 liters and 8 liters respectively (0,8), that counts as one "move". Instead, if you had poured from bucket one into bucket two until bucket two was full, leaving you with 4 liters in bucket one and 11 liters in bucket two (4,11), that would count as only one "move" as well.

To conclude, the only valid moves are:

- pouring from one bucket to another
- emptying one bucket and doing nothing to the other
- filling one bucket and doing nothing to the other

Written with <3 at Fullstack Academy by Lindsay Levine.

Refer to the exercism help page for Rust installation and learning resources.

Execute the tests with:

```
$ 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 tests without editing the tests source file, use:

```
$ cargo test -- --ignored
```

To run a specific test, for example `some_test`

, you can use:

```
$ cargo test some_test
```

If the specific test is ignored use:

```
$ cargo test some_test -- --ignored
```

To learn more about Rust tests refer to the online test documentation

Make sure to read the Modules chapter if you haven't already, it will help you with organizing your files.

After you have solved the exercise, please consider using the additional utilities, described in the installation guide, to further refine your final solution.

To format your solution, inside the solution directory use

```
cargo fmt
```

To see, if your solution contains some common ineffective use cases, inside the solution directory use

```
cargo clippy --all-targets
```

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.

The 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.

Water Pouring Problem http://demonstrations.wolfram.com/WaterPouringProblem/

It's possible to submit an incomplete solution so you can see how others have completed the exercise.

```
use two_bucket::{solve, Bucket, BucketStats};
#[test]
fn test_case_1() {
assert_eq!(
solve(3, 5, 1, &Bucket::One),
Some(BucketStats {
moves: 4,
goal_bucket: Bucket::One,
other_bucket: 5,
})
);
}
#[test]
#[ignore]
fn test_case_2() {
assert_eq!(
solve(3, 5, 1, &Bucket::Two),
Some(BucketStats {
moves: 8,
goal_bucket: Bucket::Two,
other_bucket: 3,
})
);
}
#[test]
#[ignore]
fn test_case_3() {
assert_eq!(
solve(7, 11, 2, &Bucket::One),
Some(BucketStats {
moves: 14,
goal_bucket: Bucket::One,
other_bucket: 11,
})
);
}
#[test]
#[ignore]
fn test_case_4() {
assert_eq!(
solve(7, 11, 2, &Bucket::Two),
Some(BucketStats {
moves: 18,
goal_bucket: Bucket::Two,
other_bucket: 7,
})
);
}
#[test]
#[ignore]
fn goal_equal_to_start_bucket() {
assert_eq!(
solve(1, 3, 3, &Bucket::Two),
Some(BucketStats {
moves: 1,
goal_bucket: Bucket::Two,
other_bucket: 0,
})
);
}
#[test]
#[ignore]
fn goal_equal_to_other_bucket() {
assert_eq!(
solve(2, 3, 3, &Bucket::One),
Some(BucketStats {
moves: 2,
goal_bucket: Bucket::Two,
other_bucket: 2,
})
);
}
#[test]
#[ignore]
fn not_possible_to_reach_the_goal() {
assert_eq!(
solve(6, 15, 5, &Bucket::One),
None
);
}
#[test]
#[ignore]
fn with_same_buckets_but_different_goal_then_it_is_possible() {
assert_eq!(
solve(6, 15, 9, &Bucket::One),
Some(BucketStats {
moves: 10,
goal_bucket: Bucket::Two,
other_bucket: 0,
})
);
}
```

```
use std::cmp;
use std::collections::{HashSet, VecDeque};
#[derive(PartialEq, Eq, Debug)]
pub enum Bucket {
One,
Two,
}
/// A struct to hold your results in.
#[derive(PartialEq, Eq, Debug)]
pub struct BucketStats {
/// The total number of "moves" it should take to reach the desired number of liters, including
/// the first fill.
pub moves: u8,
/// Which bucket should end up with the desired number of liters? (Either "one" or "two")
pub goal_bucket: Bucket,
/// How many liters are left in the other bucket?
pub other_bucket: u8,
}
/// Solve the bucket problem
pub fn solve(
capacity_1: u8,
capacity_2: u8,
goal: u8,
start_bucket: &Bucket,
) -> Option<BucketStats> {
// Solution uses BFS to find shortest path to goal
let mut visited = HashSet::new();
let mut to_visit = VecDeque::new();
match start_bucket {
Bucket::One => {
to_visit.push_back(((capacity_1, 0), 1));
visited.insert((0, capacity_2));
}
Bucket::Two => {
to_visit.push_back(((0, capacity_2), 1));
visited.insert((capacity_1, 0));
}
}
while let Some((state, moves)) = to_visit.pop_front() {
visited.insert(state);
match state {
(b1, b2) if b1 == goal => {
return Some(BucketStats {
other_bucket: b2,
moves,
goal_bucket: Bucket::One,
})
}
(b1, b2) if b2 == goal => {
return Some(BucketStats {
other_bucket: b1,
moves,
goal_bucket: Bucket::Two,
})
}
_ => {
let new_states =
get_new_states(state, &visited, capacity_1, capacity_2);
to_visit.extend(new_states.into_iter().map(|s| (s, moves + 1)));
}
}
}
None
}
fn get_new_states(
(b1, b2): (u8, u8),
visited: &HashSet<(u8, u8)>,
capacity_1: u8,
capacity_2: u8,
) -> Vec<(u8, u8)> {
let pour_1 = cmp::min(b1, capacity_2 - b2);
let pour_2 = cmp::min(b2, capacity_1 - b1);
let moves = [
// Fill the buckets
(capacity_1, b2),
(b1, capacity_2),
// Empty the buckets
(0, b2),
(b1, 0),
// Pour from bucket to bucket
(b1 - pour_1, b2 + pour_1),
(b1 + pour_2, b2 - pour_2),
];
moves.into_iter().filter(|s| !visited.contains(s)).cloned().collect()
}
```

A huge amount can be learned from reading other people’s code. This is why we wanted to give exercism users the option of making their solutions public.

Here are some questions to help you reflect on this solution and learn the most from it.

- What compromises have been made?
- Are there new concepts here that you could read more about to improve your understanding?

Level up your programming skills with 3,089 exercises across 52 languages, and insightful discussion with our volunteer team of welcoming mentors.
Exercism is
**100% free forever**.

## Community comments