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

Assorted cleanups #5059

Closed
wants to merge 9 commits into from
Closed

Conversation

bench: 1303971
bench: 1303971
bench: 1303971
bench: 1303971
bench: 1303971
bench: 1303971
bench: 1303971
@pb00067
Copy link

pb00067 commented Mar 4, 2024

I propose to change uci.h line 52 from
static std::string move(Move m, bool chess960);
to
static std::string move(Move m, bool chess960 = false);

because it is very annoying being always forced to write
UCI::move(move, pos.is_chess960())
instead to simply write
UCI::move(move)
when printing some debug info to the console.
I think people does understand that they have to use UCI::move(move, pos.is_chess960()) when analyzing chess960 positions, but I think it´s a extreme rarely use-case.

@Disservin
Copy link
Member

@pb00067 I get your suggestion but a) I don’t like all the many comment changes in this pr, it‘s also why it wasn’t merged. b) I see the value from the default argument but I think it will attract bugs which will be noticed only when it’s too late.

@FauziAkram
Copy link
Contributor Author

a) I don’t like all the many comment changes in this pr, it‘s also why it wasn’t merged. b) I see the value from the default argument but I think it will attract bugs which will be noticed only when it’s too late.

@Disservin Which are the changes that you don't like, so I will revert them.
Basically, there are currently 4 changes:

  1. Elo worth updates.
  2. Capitalize the first letter of the comment.
  3. Let the sentence complete in the same row as long as the length of the sentence allows it.
  4. the comment about 20% time is outdated due to tuned merged patches, so changed it to a more general "percentage".

@Disservin
Copy link
Member

I already said that I won’t merge arbitrary comment changes. I’ll only merge something where the comment is fundamentally wrong.

@FauziAkram
Copy link
Contributor Author

@Disservin So that means that I need to revert number 1,2,3. Right?

@Disservin
Copy link
Member

Yes, though the elo worth updates can be kept, also remove your reordering of the includes. Regarding 4) i later gotta check what we do. It's probably easier to start fresh and add the new changes

@FauziAkram
Copy link
Contributor Author

Ok, PR closed, and started fresh as suggested.

@FauziAkram FauziAkram closed this Mar 4, 2024
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.

3 participants