forgeronvirtuel

Name:Unknown

Clan:Unknown

Member Since:Feb 2018

Last Seen:Apr 2023

Profiles:

Following:0

Followers:0

Allies:0

- forgeronvirtuel
- commented on "Tribonacci Sequence" go solution
- 3 years ago
+1 this solution is clearly not optimised
- forgeronvirtuel
- commented on "Reversed sequence " go solution
- 3 years ago
This comment is hidden because it contains spoiler information about the solution
- forgeronvirtuel
- commented on "Reversed sequence " go solution
- 3 years ago
This comment is hidden because it contains spoiler information about the solution
- forgeronvirtuel
- commented on "Reversed sequence " go solution
- 3 years ago
This comment is hidden because it contains spoiler information about the solution
- forgeronvirtuel
- commented on "Reversed sequence " go solution
- 3 years ago
This comment is hidden because it contains spoiler information about the solution
- forgeronvirtuel
- commented on "Reversed sequence " go solution
- 3 years ago
This comment is hidden because it contains spoiler information about the solution
- forgeronvirtuel
- commented on "Beginner - Reduce but Grow" go solution
- 3 years ago
This comment is hidden because it contains spoiler information about the solution
- forgeronvirtuel
- commented on "Bouncing Balls" go solution
- 3 years ago
I'm surprised this is the best practice:
- reuse of a parameter (h): I think it is always better to redefine new variable
- since go have this assignement feature :=, should we not use it ?
Also I wonder if it is not faster to compute if we use the mathematics formulas.