Introduced sin and cos in runtime

[maxonfjvipon]

No description provided.

[yegor256]

@maxonfjvipon I think it would be better to have float.cos and float.sin instead of cos and sin standalone objects.

[codecov]

Codecov Report

Merging #598 (c4c74a2) into master (5406f43) will increase coverage by 0.06%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #598      +/-   ##
============================================
+ Coverage     80.82%   80.88%   +0.06%     
  Complexity      477      477              
============================================
  Files           133      135       +2     
  Lines          2487     2495       +8     
  Branches        222      222              
============================================
+ Hits           2010     2018       +8     
  Misses          404      404              
  Partials         73       73              

Impacted Files	Coverage Δ
...me/src/main/java/EOorg/EOeolang/EOfloat$EOcos.java	100.00% <100.00%> (ø)
...me/src/main/java/EOorg/EOeolang/EOfloat$EOsin.java	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5406f43...c4c74a2. Read the comment docs.

[maxonfjvipon]

@yegor256 please check this out. If it's good I would continue to add more objects like these.
Also I wanted to ask about these objects written in eo: should I make a PR at this repository or at objectionary?

[yegor256]

@maxonfjvipon all looks good now, but you also should add these two "methods" to float.eo file. Otherwise, they won't be visible by EO compiler. No need to touch "objectionary": your objects will appear there automatically, once we release a new version of this repository to Maven Central.

[yegor256]

@maxonfjvipon also, would be nice if you would add some tests to float-tests.eo.

[maxonfjvipon]

@yegor256 Ok. Will be done soon

[yegor256]

@maxonfjvipon if you think that the PR is ready for merging, say so explicitly by posting a new message. Otherwise, it will hang in there forever :)

[maxonfjvipon]

@yegor256 Oh, my bad) I think the PR is ready to merge

[yegor256]

@rultor merge

[rultor]

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

[rultor]

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 7min)

[yegor256]

@maxonfjvipon thanks!

[0crat]

Job gh:cqfn/eo#598 is not assigned, can't get performer