-
-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Opti + typo #108
Opti + typo #108
Conversation
Pourquoi as-tu enlevé tous les commentaires dans getAverage ? |
Les noms de fonctions me paraissaient assez explicites, et leur fonctionnement pas si compliqué que ça |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
globalement LGTM
Alors certes, mais je trouve que la méthode de calcul parrait assez contre-intuituve pour devoir être précisée (notamment pour les débiles comme moi qui n'y pipent rien en maths) |
Bruh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
sérieux ? de l'IA ? par chez nous ? |
Pour commenter 15 lignes ça devrait aller, mais je l'aurais fait si j'avais pu ce matin ;) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, ça fonctionne chez moi dumoins
perf: optimizing getAverages
&
chore: update "made with love with ..." message