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

Implementing data validation #209

Closed
wants to merge 36 commits into from

Conversation

mrKappen
Copy link

@mrKappen mrKappen commented Oct 2, 2018

Added utility methods that do the following:

  1. to_upper_case : takes a string input and returns an uppercase string output
  2. to_lower_case: takes a string input and returns a lowercase string output
  3. get_random_double: takes a min and max to form a range and returns a double within that range
  4. get_random_int: takes a min and max to form a range and returns an integer within that range

This PR closes issue #99

faheel and others added 30 commits February 14, 2018 13:02
* remove main() and make n_queens a header file
* move functions inside NQueensSolver class
and drop ".test" from tests
* add commands for installing CMake 3.10
* update build command
and add build entry in CMakeLists
* call solve() in the constructor to guarantee that the puzzle has been solved when calling any public method
* show_solution -> print_solution
…#200)

Importing the `std` namespace can lead to namespace pollution. This commit replaces those namespace directives with more specific ones, such as `using std::cin`.
alxmjo and others added 6 commits September 13, 2018 20:28

Refactor greatest common denominator algorithm to use a header file. Add test
cases as .cpp file to test. Also fix an error in greatest common denominator
function that prevented the accurate calculation of negative arguments. Update
README.

* Migrate extended Euclidean to header, unit tests

Removes old .cpp file for the extended Euclidean algorithm and adds unit
 tests. Also updates README.

* Fix accidental addition of old denominator files
@mrKappen
Copy link
Author

mrKappen commented Oct 2, 2018

Hey @alxmjo I have submitted a pull request making the utility functions requested in issue #99 , but it was rejected. I am not really sure I understand why. Do I need to create unit tests for utility functions? Should I improve my comments? Thanks!

@alxmjo
Copy link
Collaborator

alxmjo commented Oct 2, 2018

Hey @alxmjo I have submitted a pull request making the utility functions requested in issue #99 , but it was rejected. I am not really sure I understand why. Do I need to create unit tests for utility functions? Should I improve my comments? Thanks!

It looks like there may be issues with how you pulled the repo and then merged back in. There are conflicts between those commits which is why you can't merge your work back in. Which files did you actually mean to modify?

And did you follow the directions here?

@alxmjo alxmjo added the Utility label Oct 2, 2018
@stale
Copy link

stale bot commented Jul 31, 2019

This issue has been automatically marked as inactive because it has not had recent activity. It will be closed in 15 days if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Inactive label Jul 31, 2019
@stale stale bot closed this Aug 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants