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.

Sign up for GitHub

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

Jump to bottom

all tracks' topics / difficulty for a given exercise #834

Closed
petertseng opened this issue Jun 20, 2017 · 0 comments
Closed

all tracks' topics / difficulty for a given exercise #834

petertseng opened this issue Jun 20, 2017 · 0 comments

Comments

@petertseng
Copy link
Member

don't mind me.

all tracks:

for i in tracks/*/config.json; do echo $i; jq '.exercises | map(select(.slug == "rectangles"))' < $i; done

only those tracks that have rated any one exercise:

for i in tracks/*/config.json; do echo $i; jq 'if any(.exercises[]; .difficulty != 1) then .exercises | map(select(.slug == "bracket-push")) else [] end' < $i; done
@petertseng petertseng mentioned this issue Jun 20, 2017
Merged
petertseng added a commit to exercism/rust that referenced this issue Jun 20, 2017
@petertseng
config: rectangles topics: replace lifetimes with algorithm (#309)
2b0231d 
This has been a long time coming.
Ever since #167 (comment) lifetimes
should not have been a topic for rectangles.
The reasons were discussed there already:

* The "Putting it All Together" problems do not emphasise Rust language
  features in general.
* The specific feature "lifetimes" is not implied by this problem. A
  sampling of ten submitted solutions shows two solutions with
  lifetimes.

I used the exercism/problem-specifications#834 command to
inspect other tracks' topics to see if we can glean any insight here.

C#/F#: parsing, transforming
Lua: strings, performance, control-flow (if/else, loops), algorithms

Based on these, my recommendation:

A possible topic is string parsing, because we are reading in a string
and trying to make sense of it. However this is not parsing in the usual
sense that one would use a parser for, which usually deals with text.

If we were to declare "string parsing" a topic of rectangles, we would
probably use it for ocr-numbers too (but we do not; the topics for
ocr-numbers are lines, slices, chunks).

"algorithm" is chosen because significant work will likely go into
devising an algorithm for determining the rectangles, since that is not
immediately obvious from the problem description.  Solutions will likely
display a diverse set of approaches.

One might surmise that the alphametics exercise could have this topic as
well, but this commit deals with rectangles only.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@petertseng