Changed filename, added non-preemptive SJF

[sangin-lee]

Describe your change:

Changed filename of previous [shortest_job_fisrt.py] to [shortest_remaining_time_first.py] because it comes under to
URL : https://en.wikipedia.org/wiki/Shortest_remaining_time

Added new [shortest_job_first.py] which is non-preemptive shortest job first. It comes under to
URL : https://en.wikipedia.org/wiki/Shortest_job_next

+Added Wikipedia URL in each comments

• Add an algorithm?
• Fix a bug or typo in an existing algorithm?
• Documentation change?

Checklist:

• I have read CONTRIBUTING.md.
• This pull request is all my own work -- I have not plagiarized.
• I know that pull requests will not be merged if they fail the automated tests.
• This PR only changes one algorithm file. To ease review, please open separate PRs for separate algorithms.
• All new Python files are placed inside an existing directory.
• All filenames are in all lowercase characters with no spaces or dashes.
• All functions and variable names follow Python naming conventions.
• All function parameters and return values are annotated with Python type hints.
• All functions have doctests that pass the automated testing.
• All new algorithms have a URL in its comments that points to Wikipedia or other similar explanation.
• If this pull request resolves one or more open issues then the commit message contains Fixes: #{$ISSUE_NO}.

[ghost]

Click here to look at the relevant links ⬇️

🔗 Relevant Links

Repository:

• Contributing guidelines
• Project Euler solution guidelines

Python:

• Formatted string literals (f-strings)
• Type hints
• doctest
• unittest
• pytest

Automated review generated by algorithms-keeper. If there's any problem regarding this review, please open an issue about it.

---

algorithms-keeper commands and options

algorithms-keeper actions can be triggered by commenting on this PR:

• @algorithms-keeper review to trigger the checks for only added pull request files
• @algorithms-keeper review-all to trigger the checks for all the pull request files, including the modified files. As we cannot post review comments on lines not part of the diff, this command will post all the messages in one comment.

NOTE: Commands are in beta and so this feature is restricted only to a member or owner of the organization.

[ghost]

Click here to look at the relevant links ⬇️

🔗 Relevant Links

Repository:

• Contributing guidelines
• Project Euler solution guidelines

Python:

• Formatted string literals (f-strings)
• Type hints
• doctest
• unittest
• pytest

Automated review generated by algorithms-keeper. If there's any problem regarding this review, please open an issue about it.

---

algorithms-keeper commands and options

algorithms-keeper actions can be triggered by commenting on this PR:

• @algorithms-keeper review to trigger the checks for only added pull request files
• @algorithms-keeper review-all to trigger the checks for all the pull request files, including the modified files. As we cannot post review comments on lines not part of the diff, this command will post all the messages in one comment.

NOTE: Commands are in beta and so this feature is restricted only to a member or owner of the organization.

[sangin-lee]

@cclauss @dhruvmanila Could you please review my work?

[sangin-lee]

Fixed doctest results
ex) 5.0 -> 5.00000

[cclauss]

As a user, I would find it very distracting to see 5.00000 instead of 5.0. All these extra zeros create unnecessary cognitive load for the reader so I would much prefer the clear and simple 5.0 instead.

[sangin-lee]

As a user, I would find it very distracting to see 5.00000 instead of 5.0.

Would it be better to modify codes to print out only first digit of the decimal point? or maybe two digits?

[cclauss]

5.12345 is OK if there are actual values there to the right of the decimal point but 5.00000 must be shortened to 5.0

[sangin-lee]

Fixed formatting. Thanks for commenting!!

[sangin-lee]

@cclauss What should I do to merge this PR?

[JiHyunSong]

@cclauss can you follow it?

[stale]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.