Skip to content
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

(Potentially) Implement New Concept Exercise: Compiling #2524

Open
junedev opened this issue Oct 25, 2022 · 3 comments
Open

(Potentially) Implement New Concept Exercise: Compiling #2524

junedev opened this issue Oct 25, 2022 · 3 comments
Labels
discussion This is a topic for a longer discussion. The issue can stay open for a while.

Comments

@junedev
Copy link
Member

junedev commented Oct 25, 2022

We have a lot of students coming from intepreted languages to Go. Those students often struggle with the fact the Go is a compiled language. They sometimes have trouble to understand the compiler error messages and/or would expect to see all the test failures instead (see exercism/go-test-runner#47).

One idea that came up how to mitigate that was to add a concept that explains more what it means to work in Go as a compiled language and how to deal with the compiler errors (especially in cases where the exercise comes without a stub). I think there are quite some things to unpack, e.g. that Go does not allow unused variables, has no compiler warnings etc.
Since we don't have concepts without coding type exercises, the exercise could be around fixing some compiler errors in existing code and maybe add one missing function. In any case, the focus would be a bit more on the content the student is supposed to read.

See also #2473 (comment) were this was mentioned.

This exercise should appear very early in the concept tree, potentially directly after basics (lasagna), definitly before functions (lasagna-master) though.

More details to be defined ...

@junedev junedev added the discussion This is a topic for a longer discussion. The issue can stay open for a while. label Oct 25, 2022
@andrerfcsantos
Copy link
Member

andrerfcsantos commented Oct 29, 2022

Since we don't have concepts without coding type exercises, the exercise could be around fixing some compiler errors in existing code and maybe add one missing function. In any case, the focus would be a bit more on the content the student is supposed to read.

I like this idea a lot. It is a powerful but gentle introduction to the language and the tooling. Puts you in control without giving you a lot of work from the start. rustlings follows the same formula and is very popular amongst learners of Rust.

@SAbruzzo
Copy link

SAbruzzo commented Mar 9, 2023

I think that this was never tackled. If nobody is working on it - I am happy to take it and contribute

@junedev
Copy link
Member Author

junedev commented Mar 9, 2023

@SAbruzzo Sorry but this repository does not accept community contributions currently. Please see https://exercism.org/blog/freeing-our-maintainers for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion This is a topic for a longer discussion. The issue can stay open for a while.
Projects
None yet
Development

No branches or pull requests

3 participants