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

Added Bucket Sort #651

Closed
wants to merge 1 commit into from
Closed

Added Bucket Sort #651

wants to merge 1 commit into from

Conversation

Sanchita1304
Copy link

@Sanchita1304 Sanchita1304 commented Oct 1, 2023

Change Summary

Added Bucket Sort

Checklist

If you haven't fulfilled the below requirements or even delete the entire checklist, your PR won't be reviewed and will be closed without notice. Regular contributors (with 10+ PRs) can skip this part.

General

  • This Pull Request is all my own work. (You'll be blacklisted if you are caught for plagiarism.)
  • I've read CONTRIBUTING.md
  • I've applied LaTex for all variables, formulas and time / space complexity instead of using backticks
  • I've started the app locally and verified all the content and all links (if applicable) are accessible correctly
  • I've included Complexity Analysis (Time Complexity & Space Complexity).
  • I've written my explanation well and it is easy to understand for beginners

Tutorial

  • I've read and followed the Tutorial Template
  • I've explained my topic well with 2 - 3 LC problems and no external problems are used.
  • I've provided the full working solutions to the problems used in this tutorial.
  • I've provided suggested problems at the end with the given format. See here as an example. If the target solution is not available, leave solutionLink blank.
  • I've given credits / references if I use external resources. (For an image, give credit under it. Otherwise, add a new section called References at the end (after Suggested Problems).)

Solutions

  • I've read and followed the Solution Template
  • I've formatted my code well with K&R Coding style
  • I've confirmed that comments are put above each line rather than writing on the same line.
  • I've included a meaningful approach name for my solution. e.g. ## Approach 1: Two Pointers.

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

Successfully merging this pull request may close these issues.

2 participants