Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upDevelopment #1786
Open
Development #1786
Conversation
add a Test about AnyBaseToDecimal.java
add some tests for Sort
delete print statements from Test files.
add Test for InsertionSort
Signed-off-by: Ralph Niemitz <[email protected]>
Negative Integer, worst case array test added
add MergeSortTest for MergeSort.
-Linear Search was added. -Made Both searches final and static ( There is no reason to have to instantiate them). Also Changed the tests to include the new static methods. -Added a new test, searching an empty array.
Added StoogeSort algorithm and JUnit Test
Added Interpolation Search and JUnit test.
Added Linear Search, changed Binary search
Add hexadecimal to binary and hexadecimal to decimal conversions
add junit for test paass
Added LFU Cache implementation
Added LRU cache implementation.
- Local variable names in java must be with the default regular expression ^[a-z][a-zA-Z0-9]*$ https://rules.sonarsource.com/java/tag/convention/RSPEC-117 - The diamond operator ("<>") should be used when the type of the maps are already defined https://rules.sonarsource.com/java/RSPEC-2293 - Package names being camel cased is a code smell
String literals should not be duplicated https://rules.sonarsource.com/java/RSPEC-1192
-Generic types shouldn't be used raw (without type parameters) in variable declarations or return values. Doing so bypasses generic type checking, and defers the catch of unsafe code to runtime. https://rules.sonarsource.com/java/RSPEC-3740 - The dangling else problem appears when nested if/else statements are written without curly braces. In this case, else is associated with the nearest if but that is not always obvious and sometimes the indentation can also be misleading. https://rules.sonarsource.com/java/tag/confusing/RSPEC-5261
Fixed code smells after running sonarqube on the project
Revert "Fixed code smells after running sonarqube on the project"
…nto Development
Added LinkedHashMap cache type params to avoid build error
…evelopment Revert "Revert "Fixed code smells after running sonarqube on the project""
Fixed actions on pull requests
Fixed syntax error
Implementation for Round Robin Algorithm in Java with tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Describe your change:
Added ROT N cipher decryptor algorithm.
References
Checklist:
Fixes: #{$ISSUE_NO}.