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

Decide where to use Quo/MulTruncate and where to use Quo/Mul #380

Closed
hallazzang opened this issue Jun 1, 2021 · 0 comments · Fixed by #413
Closed

Decide where to use Quo/MulTruncate and where to use Quo/Mul #380

hallazzang opened this issue Jun 1, 2021 · 0 comments · Fixed by #413
Assignees
Labels
enhancement New feature or request

Comments

@hallazzang
Copy link
Contributor

During the calculations we use sdk.Dec.Quo and sdk.Dec.Mul extensively, but there are also sdk.Dec.QuoTruncate and sdk.Dec.MulTruncate.
We need to determine which methods suit better for which situation.

@hallazzang hallazzang added the enhancement New feature or request label Jun 1, 2021
hallazzang added a commit to b-harvest/liquidity that referenced this issue Jun 2, 2021
dongsam pushed a commit that referenced this issue Jun 3, 2021
* keep zero reserve coins from GetReserveCoins

* treat pool with zero pool coin supply as depleted

also change Mul/QuoTruncate to Mul/Quo.

fixes #364

* rollback change of Quo/MulTruncate to Quo/Mul

this should be done in #380
dongsam pushed a commit that referenced this issue Jun 8, 2021
* keep zero reserve coins from GetReserveCoins

* treat pool with zero pool coin supply as depleted

also change Mul/QuoTruncate to Mul/Quo.

fixes #364

* rollback change of Quo/MulTruncate to Quo/Mul

this should be done in #380

* treat a pool with zero reserve coin as depleted
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants