[Go] Concepts needed to solve the v2 two fer exercise #233
Conversation
|
I'd leave this open for a few days so others can also review it |
| ### Linting | ||
|
|
||
| It's the first time most students work with go, and many have not yet used `golint`. Linting already provides some hints | ||
| on what (not) to do, eg use of variable names, not using else if the the regular condition ends with return, and missing |
There was a problem hiding this comment.
This isn't quite clear to me (what does 'use of variable names' mean? You should use them? You shouldn't use them?)
Co-Authored-By: Gabriel Nelle <tehsphinx@web.de>
Co-Authored-By: John Arundel <john@bitfieldconsulting.com>
tehsphinx
force-pushed
the
go-twofer-concepts
branch
from
1151d3d
to
c550f92
Compare
|
I rebased this so the link-checkers work now |
Co-Authored-By: Victor Goff <keeperotphones@gmail.com>
Co-Authored-By: Victor Goff <keeperotphones@gmail.com>
Co-Authored-By: Victor Goff <keeperotphones@gmail.com>
Co-Authored-By: Victor Goff <keeperotphones@gmail.com>
Co-Authored-By: Victor Goff <keeperotphones@gmail.com>
Co-Authored-By: Victor Goff <keeperotphones@gmail.com>
|
Just as a side node: These And they will help us later to define the prerequisites of a practice exercise (v2 exercise) which in turn defines the tree of exercises that needs to be finished before a practice exercise will be unlocked. What these PRs are not for is to determine how to solve an exercise in an idiomatic way. It's not about right vs wrong, good vs bad, fast vs slow, etc. It's purely about which concepts are (commonly) used to solve this. |
Co-Authored-By: John Arundel <john@bitfieldconsulting.com>
Co-Authored-By: John Arundel <john@bitfieldconsulting.com>
solves #230