Approved! Thank you.

Approved! Thank you.

Thanks! Approved

Thank you for pointing this out. I updated the Python and JS tests to use a=1 instead of a=0.

Thanks! Approved

The comment above the return statement is part of the source code. I use the built-in inspect package to get the source code of the current script as a string and return the contents of the comment.

Mistake in instructions.

Each rectangle is represented by four integers [x0, y0, x1, y1], where (x0, y0) is the lower-left corner and (x1, y1) is the upper-left corner.

(x1, y1) is the upper-right corner, not the upper-left.

Cannot be completed in Rust (1.66). A compilation error occurs when attempt to submit any solution (sample test cases work though)

fn max_sum_between_two_negatives(nums: &Vec<i32>) -> Option<i32> {
    Some(1)
}

Attempt results in

error[E0599]: no method named `tuple_windows` found for struct `Map` in the current scope
  --> src/lib.rs:19:10
   |
19 |         .tuple_windows::<(_, _)>()
   |          ^^^^^^^^^^^^^ method not found in `Map<Filter<Enumerate<std::slice::Iter<'_, i32>>, [closure@src/lib.rs:17:17: 17:25]>, [closure@src/lib.rs:18:14: 18:22]>`

For more information about this error, try `rustc --explain E0599`.
error: could not compile `challenge` due to previous error


NOTE: Line numbers in error messages can be incorrect due to concatenation.

All the coins have to meet on the same vertex, not just two of them. u1 and u2 can stay together since they start on the same vertex but they need to meet up with u3.

Did your "attempt" results have any red text in the output? If you passed all the tests when you click "attempt" then the output should display all green messages and the "attempt" button will become "submit".

Log is what gets printed to the output stream so maybe you printed the string rather than writing a function to return it?

approved!

Looks good to me

Python

If the test suite happens to use a reference solution to calculate expected values (which should be avoided when possible), or some kind of reference data like precalculated lists, etc., it must not be possible for the user to redefine, overwrite or directly access its contents. To prevent this, it should be defined in a scope local to the testing function, a it or a describe block.

The reference solution or data must not be defined in the Preloaded code. The reference solution must not be defined in the top-level scope of the test suite.