Skip to content

saddle-points: Added efficiency notice about vector of vectors#789

Merged
petertseng merged 3 commits intoexercism:masterfrom
michalfita:787-Saddle_Points_Note
Feb 15, 2019
Merged

saddle-points: Added efficiency notice about vector of vectors#789
petertseng merged 3 commits intoexercism:masterfrom
michalfita:787-Saddle_Points_Note

Conversation

@michalfita
Copy link
Copy Markdown
Contributor

In reference to my issue #787 this is proposed notice in the exercise description about inefficiency of vector of vectors and cache locality aspect.

Update to README.md seem to pick up some changes from master exercise repository.

I'm open to any suggestions about wording.

Copy link
Copy Markdown
Member

@coriolinus coriolinus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for submitting this PR, @michalfita! It looks generally good to me. I have several suggestions to make the English flow more smoothly, but none are critical enough to block the PR.

I will now leave this PR open for several days to give other maintainers the chance to comment on it. I intend to merge this not later than Monday the 18th. If on Tuesday I still haven't, please feel free to ping me a reminder.

Comment thread exercises/saddle-points/.meta/hints.md Outdated
Comment thread exercises/saddle-points/.meta/hints.md Outdated
this exercise is designed to help students understand basic concepts about
vectors, such as indexing, and that nested data types are legal, _vector of
vectors_ is a suboptimal choice for high-performance matrix algebra and any
similar efficient processing of larger amount of data.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
similar efficient processing of larger amount of data.
similar efficient processing of larger amounts of data.

Comment thread exercises/saddle-points/.meta/hints.md Outdated
Comment thread exercises/saddle-points/.meta/hints.md Outdated
Comment thread exercises/saddle-points/.meta/hints.md Outdated
Comment thread exercises/saddle-points/.meta/hints.md Outdated
@michalfita
Copy link
Copy Markdown
Contributor Author

@coriolinus Thanks. I approved your suggestions, but that created another commit. I'm not sure if it's acceptable by Exercism rules for PRs? The guide says PR should consist of one commit.

@coriolinus
Copy link
Copy Markdown
Member

coriolinus commented Feb 13, 2019 via email

@michalfita
Copy link
Copy Markdown
Contributor Author

Ups... I need to regenerate locally on my PC.

@petertseng
Copy link
Copy Markdown
Member

for PRs that include changes from problem-specifications, please link the relevant PRs.

It is exercism/problem-specifications#1429 for this one.

When merging, we should include that in the commit message.

@michalfita
Copy link
Copy Markdown
Contributor Author

@petertseng Is it natural they've been picked up when I updated README.md? Or did I do something unnecessary? To be honest I had to guess what I need to do to get that one exercise updated.

@petertseng petertseng added the sync/readme Keep a README in sync with exercism/problem-specifications label Feb 14, 2019
@petertseng
Copy link
Copy Markdown
Member

Is it natural they've been picked up when I updated README.md?

If we assume the tool that was used conforms to the specification of https://github.com/exercism/docs/blob/master/language-tracks/exercises/anatomy/readmes.md#the-readme-template , then that is what will happen.

Or did I do something unnecessary?

And, as you may have gotten a hint of with Travis CI, we have a check for that in Travis CI so that we do not get too out of date... therefore any PR that changes saddle-points has to do that, for better or for worse. It's good for making sure nothing accidentally gets missed.

@petertseng petertseng force-pushed the 787-Saddle_Points_Note branch from f458bfc to 59fb6da Compare February 15, 2019 03:04
@petertseng
Copy link
Copy Markdown
Member

I think it is wiser to separate the problem-specifications changes from the changes made in this PR. So, I have done so.

@petertseng
Copy link
Copy Markdown
Member

Thanks!

petertseng pushed a commit that referenced this pull request Nov 2, 2019
exercism/problem-specifications#1429 which was
applied to this track in #789 uses
one-based indices in the README.

The track still uses zero-based indices in the tests. This inconsistency
is a potential source of student confusion. Prevent student confusion by
explaining the inconsistency.

Closes #791
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

sync/readme Keep a README in sync with exercism/problem-specifications

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants