Skip to content

Porting zipper with recursion-schemes #851

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

Closed
zhujinxuan opened this issue Oct 1, 2019 · 8 comments
Closed

Porting zipper with recursion-schemes #851

zhujinxuan opened this issue Oct 1, 2019 · 8 comments

Comments

@zhujinxuan
Copy link

zhujinxuan commented Oct 1, 2019

Hi, I find the zipper is not implemented yet. I can do it with recursion-schemes (because it is fun).

I can make a PR once you think it is good.

Cheers,
Jinxuan Zhu

@petertseng
Copy link
Member

I wasn't sure what this means. Since you linked to https://github.com/exercism/haskell/tree/master/exercises/zipper, it is clear to see that the zipper exercise is already implemented. Was there a different exercise you were thinking of implementing?

@zhujinxuan
Copy link
Author

@petertseng Sorry, I made a mistake on the purpose of the project. I thought it was about giving solutions instead of giving exercises.

Sorry, my mistake. I will close this issue.

@sshine
Copy link
Contributor

sshine commented Oct 2, 2019

@zhujinxuan: The example solutions that inhabit this repository mainly show that a solution is possible and serves to validate the test suite. Sometimes there are multiple examples for a single exercise, but mainly when the exercise can be solved with different configurations.

E.g. if a solution can be solved with Data.Text rather than String, we'd like to know that changes to the test suite does not break overloading between those options. When different solutions are encapsulated entirely by the interface, they're better off in the "community solutions" on the website (which needs an overhaul to be truly useful).

You are very welcome to port something else;

$ jq -r --argjson canonical \
        "$(cd ~/exercism/problem-specifications/exercises \
           && printf '%s\0' * | jq -R 'sub("\u0000$"; "") | split("\u0000")')" \
    '$canonical - (.exercises | map(.slug)) | .[]' config.json
affine-cipher
book-store
circular-buffer
counter
darts
diffie-hellman
dot-dsl
error-handling
flatten-array
grep
hangman
high-scores
knapsack
ledger
markdown
micro-blog
nucleotide-codons
paasio
point-mutations
rational-numbers
react
rectangles
resistor-color
resistor-color-trio
rest-api
reverse-string
satellite
scale-generator
tournament
tree-building
two-bucket
two-fer
variable-length-quantity
word-search

(tree-building is a work in progress in #835, though; I have several drafts for some of them that I haven't gotten around to finishing, so I won't let that discourage you from picking freely among the rest.)

@Javran
Copy link

Javran commented Feb 26, 2021

Just a side note that I was trying to find a list of problems not yet ported and wrote a script to do that, may as well share it here: https://gist.github.com/Javran/ac02edfe611b8dd88e9aae0699f77eff

@sshine
Copy link
Contributor

sshine commented Feb 26, 2021

That's cool. :) The jq script that does the same above is from the Exercism jq Cookbook. It was later supplemented by @SleeplessByte's track tracking page, but this no longer shows non-implemented practice exercises. It now shows but rather shows the migration progress for Exercism v3 in an attempt to motivate those tasks being fulfilled first.

@Javran
Copy link

Javran commented Feb 26, 2021

Thanks for the link to cookbook and tracker! I do appreciate monitoring and live visualization whenever they show up :)

@SleeplessByte
Copy link
Member

(track tracking page on the dashboard is back up! :D)

@SleeplessByte
Copy link
Member

https://tracks.exercism.io/haskell/main/unimplemented

Hard refresh if you get a white page / error. You have a broken cached version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants