-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Go Path #237
Comments
@msgehard I created this issue for you and others that are knocking out the Go assignments. |
I'm wondering if it would be possible to open up the completed Go assignments so that we can work through them as they're being completed? |
There's nobody around to nitpick Go assignments at the moment, so opening it up would likely leave people frustrated and waiting for feedback. When I know that we have two or three people who understand the idioms and best practices in Go, then I'll open it up. @levicook said he'd be willing to nitpick, but I don't want to leave him with the sole responsibility. |
What requirements are you looking for to help nitpick Go assignments? I wouldn't mind helping out, and may be able to ask around to see if others are willing to help. I want to make Go in exercism.io a reality! |
Fantastic. Me too :) I need people who can look at some Go code and make keen observations about Go conventions and idioms and how this bit of code uses the Go language effectively, or how one could use the Go language more effectively. I'd also love help making sure that both the tests and the example code follow good practices and conventions so that we're not leading people astray from the start. |
Well as I said I will be more than willing to help out, I have been using On Fri, Oct 18, 2013 at 9:38 AM, Katrina Owen notifications@github.comwrote:
|
Excellent. I'll do that. I'm going to aim for getting 20 exercises ready (we have 12 so far), then launch the path, and then aim for getting the rest of the exercises live following the launch. @vendion, @levicook, would you mind taking a look at the existing exercises in Essentially I'd like to sanity check the tests and example code to make sure they're not making any obvious blunders, and are reasonable examples of what good Go code would look like. |
Thanks everyone! |
I started hamming under #1007 -- tests are written, implementation is up next. |
I think the hamming example is in decent shape; I'm going to try linked-list next. |
Sure, where do I go to "stop by"? |
One thing that would make nitpicking easier, is if in the Nitpick screen there was a link to the documentation (if available) and the test file(s) that goes with the assignment. I'm sure this also belongs in another issue, if so sorry about the spam. |
I'll create a new issue for that. Thank you! |
Superseded by exercism/go#3 |
Add dialyzer to ci
To bring the Go path up to the same standard as the Ruby Path the following exercises need to be converted:
The text was updated successfully, but these errors were encountered: