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

Implement FIFO\Queue pool #8

Open
ravsii opened this issue May 3, 2023 · 3 comments
Open

Implement FIFO\Queue pool #8

ravsii opened this issue May 3, 2023 · 3 comments
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@ravsii
Copy link
Owner

ravsii commented May 3, 2023

I don't know how exactly to do that right now in terms of API. Could be as a separate pool, or an options to NewPool()

Related: #7

@ravsii ravsii added enhancement New feature or request help wanted Extra attention is needed good first issue Good for newcomers labels May 3, 2023
@ravsii
Copy link
Owner Author

ravsii commented May 4, 2023

Bro, this looks straight up copy-pasted from ChatGPT, and it's not even related to the project.

E: There was another comment that was deleted

@mtnvdsk
Copy link

mtnvdsk commented May 4, 2023

I am new to contribution ,can I know what is the project your issue is?

@ravsii
Copy link
Owner Author

ravsii commented May 4, 2023

Hey, @mtnvdsk .
I could write a detailed explanation a bit later, but shortly, the problem is:
Currently we have a basic pool (pool.go) that accepts players and returns found matches based on players' elo rating. There's a how-it-works diagram in README.

We'd probably more types of pools, which will have different "match found" algorithm, so FIFO is one of them (obviously it just matches players without comparing their Rating).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants