Rename Participant to Bid

[squadgazzz]

Description

Follows a suggestion from another PR, that basically renames the Participant struct into Bid, which makes more sense since this Bid now contains the score data.

Changes

• The naming itself
• Docs
• Only the DB auction participants remain, which are basically participant addresses, which are valid names.

How to test

Existing tests.

[gemini-code-assist]

Summary of Changes

Hello @squadgazzz, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs a significant refactoring by renaming the Participant struct to Bid. This change improves the clarity and accuracy of the domain model, as the Bid struct now explicitly includes score data, making its purpose more evident within the auction and winner selection process. The refactoring involved updating the struct definition, file names, imports, and all instances where the Participant type was used or referenced throughout the application.

Highlights

• Core Type Renaming: The Participant struct has been renamed to Bid across the codebase. This change reflects a more accurate terminology, especially since this struct now encapsulates score data related to auction bids.
• File Renaming: The file crates/autopilot/src/domain/competition/participant.rs has been renamed to crates/autopilot/src/domain/competition/bid.rs to align with the new struct name.
• Codebase-Wide Refactoring: All references, imports, function parameters, and variable names related to Participant have been updated to Bid in affected modules, including mod.rs, winner_selection.rs, persistence/mod.rs, run_loop.rs, and shadow.rs.
• Documentation and Comment Updates: Comments and documentation within the state.rs module and other relevant files have been adjusted to reflect the new Bid terminology and remove mentions of 'participant' where 'solution' or 'bid' is more appropriate.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request renames the Participant struct to Bid across the codebase, primarily within the autopilot crate's domain/competition module and its related files (bid.rs, mod.rs, winner_selection.rs). This change includes updating struct definitions, impl blocks, type aliases, function signatures, variable names, and doc comments to reflect the new Bid terminology. The winner-selection/src/state.rs file also had its documentation adjusted to remove references to 'participant'. A review comment specifically suggested renaming the solutions parameter to bids and the closure variable s to b in the filter_winners test helper function for consistency with the new Bid naming convention.

[m-sz]

LGTM