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

ERROR: MonotonicUpperBound requires CapLatestVersion #51

Open
oxinabox opened this issue Jun 1, 2022 · 1 comment
Open

ERROR: MonotonicUpperBound requires CapLatestVersion #51

oxinabox opened this issue Jun 1, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@oxinabox
Copy link

oxinabox commented Jun 1, 2022

Is there a reason for this requirement?
It seems like it would still be useful to be monotonic except for the latest version.

@DilumAluthge
Copy link
Member

cc: @timholy

I think the rationale is, "monotonic with respect to what"? I.e. we are monotonic with respect to the cap on the latest version, which only makes sense if the latest version is capped.

But I see the use case here. We'd need to have a way of saying:

  1. Don't cap the latest version
  2. Cap the second latest version.
  3. Use the cap on the second latest version as the starting point (or ending point, rather) for determining the monotonically increasing caps.

@DilumAluthge DilumAluthge added the enhancement New feature or request label Jun 1, 2022
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

No branches or pull requests

2 participants