Why not utilize concurrency? :)

Nice job bro !

You should invoke defer AFTER checking for error, not before.
https://pkg.go.dev/net/http#Client.Do

wow

wow

Points for creativity. I do feel like this sets a precidence for scope creep. The brief was quite specific.

Yeah as far as style points go I like this one.

Hi there.

My code is working both on my machine and on Rust Playground. However, the testing system returns the folowing error:
"called Result::unwrap() on an Err value: ParseIntError { kind: PosOverflow }"

Am I missing something or is the testing system failing wrongly?

Here's the link to playground and my code:

https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=0b8fef83a1dca09af99986ed012ff56d

fn calc(s: &str) -> u32 {
     let mut total1 = String::new();
     for c in s.chars() {
         total1.push_str(&(c as u32).to_string())
     }
     let total2 :String = total1.replace("7", "1");
     println!("{} {}", total1, total2);
     total1.parse::<u32>().unwrap() - total2.parse::<u32>().unwrap()
}

fn main() {
     println!("{}", calc("ABC"));
}

That test in Go is wrong (or the instructions aren't clear enough), in Python it expects 0:

test.assert_equals(SumEvenFibonacci(1), 0)

Check Unnamed's issue below.

The only failing test case says: "Should return 2 for input 1"

How can that possibly be?
The Fibonacchi sequence is 0, 1, 1, 2, 3, 5, ... etc.
Ok, suppose we reduce that to what the author suggests 1, 2, 3, 5, ... etc.
But then in both cases the biggest numbers equal or less the input limit 1 is
1 or [0, 1, 1] where 1 is odd and can not add to the sum and 0 (0 % 2 == 0) doesn't add to the sum either.

What is the author trying to say by this test case? Am I missing something? Is this poor wording of the kata or is this my poor English?

The kata itself is piece of cake. But I had real hard time getting throught the description :(

Also,

strings.Split(s, " ") is equvalent to string.Fields(s)

I'd say the proper way is:

import "unicode/utf8"

utf8.RuneCountInString()

Seen this on Go blog.
Cheers :)

XDDDDD

Same problem happens with C++