[CALCITE-6543] Change the RelOptCostImpl toString method to be consistent with VolcanoCost

[ChengJie1053]

[caicancai]

I think this PR deserves a jira case

[ChengJie1053]

I think this PR deserves a jira case

Ok, thanks for reviewing the code for me

[ChengJie1053]

I think this PR deserves a jira case

Hello, jira has been created
https://issues.apache.org/jira/projects/CALCITE/issues/CALCITE-6543?filter=allissues

[caicancai]

It would be best to have a test example to illustrate

[ChengJie1053]

Ok, thanks for reviewing the code for me

[mihaibudiu]

Ideally you should avoid code duplication, especially when the control-flow is so complicated.
In this case you should probably create a static method that takes a double and returns a string, and call it from both places.

[ChengJie1053]

Ideally you should avoid code duplication, especially when the control-flow is so complicated. In this case you should probably create a static method that takes a double and returns a string, and call it from both places.

Ok, thank you for helping me review the code, I will modify this place

[ChengJie1053]

Ideally you should avoid code duplication, especially when the control-flow is so complicated. In this case you should probably create a static method that takes a double and returns a string, and call it from both places.

Hello, the modified code has been submitted. If there is any problem, I will modify it again

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
59.1% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[caicancai]

@ChengJie1053 You should not squash. Wait until no one else has any comments, then squash. We need to know what you changed in each commit, so that it is better to review.

[ChengJie1053]

squash

Ok, thank you. I mistakenly thought that every commit requires a squash commit. I will pay attention to that in the future