Skip to content

gigasecond: Completely rewrite the exercise or deprecate it. #230

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
Closed
rbasso opened this issue Jul 26, 2016 · 2 comments
Closed

gigasecond: Completely rewrite the exercise or deprecate it. #230

rbasso opened this issue Jul 26, 2016 · 2 comments
Labels
question

Comments

@rbasso
Copy link
Contributor

rbasso commented Jul 26, 2016 •
edited
Loading

The way it is now, gigasecond has some problems:

  • It is too easy and boring.
  • All answers are almost the same: fromDay = addUTCTime 1e9
  • Does not match exercism/x-common/gigasecond.json.

Seems that, at least in other tracks, it can be interesting: #192 (comment)

In the Go track gigasecond is a fantastic exercise. People tackle it in so many different ways, and there are myriad opportunities to talk about idioms in the language and certain language features.

I think that if it can be turned into a more interesting exercise, then that's worth doing. If not, just deprecate it.

Edit: This exercise was changed in branch hspec-fail-fast. Please use that branch for any PR related to it or wait until it's merged in master.
@kytrinyx
Copy link
Member

kytrinyx commented Aug 1, 2016

I'm totally OK with deprecating it if it's too boring and we can't come up with a more interesting variant.

@rbasso
Copy link
Contributor Author

rbasso commented Sep 3, 2016

Until now, there is no proposal about how to make gigasecond an interesting exercise, so I think it's best to deprecate it now. If anyone finds a way to make it a good exercise in Haskell, we can easily undeprecate it.

@rbasso rbasso mentioned this issue Sep 3, 2016
Merged
@sshine sshine mentioned this issue Jan 13, 2020
Merged
sshine added a commit that referenced this issue Jan 14, 2020
@sshine
resistor-color: Mark exercise as foregone (#888)
ba96396 
resistor-color-duo was added in #808.

resistor-color-trio was added in #869.

Yet there is no resistor-color. I argue that there shouldn't be.

A reasonable solution might look like

```haskell
data Color = ...
  deriving (Eq, Enum, Bounded)

colorCode :: Color -> Int
colorCode = fromEnum

colors :: [Color]
colors = [minBound..]
```

which makes it approximately as simple as the gigasecond exercise which
was marked as deprecated in #280 (decision made in #230). Still, if it
is simply missing, it will appear as an exercise that is potentially
implementable on https://tracks.exercism.io/haskell/master/unimplemented

Since a question was raised about this exercise once, marking it as
foregone will limit further requests made in vain.
@sshine sshine mentioned this issue Apr 21, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kytrinyx @rbasso