Add and fix Algorithms

[AripaStudio]

fix ceil
add floor
add round
add gcd
add lcm
add is_prime
add prime_sieve

[TolstopyatovIlya]

In principle, everything is fine, but it is better to use /**/ in order to preserve the style, as well as asserts to package in unittests.

[AripaStudio]

Hi! Thanks for the review.

I have updated the documentation comments to use the standard /** */ block format and removed the module declarations to match the project's style.

Regarding the unittests: all my assertions are already packaged inside unittest blocks. Did you mean I should completely remove the empty void main() {} function from the bottom of the files?

Please let me know so I can clean it up. Thanks!
@TolstopyatovIlya

[TolstopyatovIlya]

I most likely confused it with unit tests, sorry.

[k1ngmang]

Unfortunately, the comments still do not follow the style defined in this repository.

[AripaStudio]

Unfortunately, the comments still do not follow the style defined in this repository.

Hi! I have updated all the documentation comments to match the repository's style guidelines.

[k1ngmang]

Unfortunately, the comments still do not follow the style defined in this repository.

Hi! I have updated all the documentation comments to match the repository's style guidelines.

No, they don't match what's in the repository. Look at the other files, they have "@param", not "Param:", and a lot of other little things. We're not accept AI slop

[AripaStudio]

Unfortunately, the comments still do not follow the style defined in this repository.

Hi! I have updated all the documentation comments to match the repository's style guidelines.

No, they don't match what's in the repository. Look at the other files, they have "@param", not "Param:", and a lot of other little things. We're not accept AI slop

Hi,

I originally used AI to help because my English isn't great, since you didn't prefer that, I manually rewrote all the comments myself using my own English and Google Translate and fixed the @param format.

[k1ngmang]

You only fixed a couple of comments. Everything needs to be adapted to javadoc comment style. Check out the other examples in the repository.

[AripaStudio]

You only fixed a couple of comments. Everything needs to be adapted to javadoc comment style. Check out the other examples in the repository.

Hi,

This time I learned about the standard D language format which is Ddoc and fixed everything. I also checked all files with "dmd -D -o-".

You were right, when I checked the HTML output first time it looked very wrong. Thanks for your guide.

[TolstopyatovIlya]

Why these ###?

[AripaStudio]

Why these ###?

HI , In Ddoc you can use Markdown, and this helps with the readability of document

[TolstopyatovIlya]

Why these ###?

HI , In Ddoc you can use Markdown, and this helps with the readability of document

This style is not standard for the current repository

[k1ngmang]

Why these ###?

HI , In Ddoc you can use Markdown, and this helps with the readability of document

This style is not standard for the current repository

We used javadoc, but I think switching everything to ddoc is a good solution.