We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Bound
Option<Self>
Now that we are using helpers for building Bounds, let's improve the syntax by making those helpers return Option<Bound> directly.
Option<Bound>
So that instead of Some(Bound::inclusive(key)) or Some(Bound::exclusive(key)), we can just write Bound::inclusive(key) / Bound::exclusive(key).
Some(Bound::inclusive(key))
Some(Bound::exclusive(key))
Bound::inclusive(key)
Bound::exclusive(key)
The text was updated successfully, but these errors were encountered:
Option
The biggest problem with this is that returning Option<Bound> will break the way we currently map our way through optional bounds:
map
cw-plus/contracts/cw1155-base/src/contract.rs
Line 497 in 4ec7985
So, voting for closing this without implementing it.
Please re-open if you see a viable alternative here.
Sorry, something went wrong.
No branches or pull requests
Now that we are using helpers for building
Bound
s, let's improve the syntax by making those helpers returnOption<Bound>
directly.So that instead of
Some(Bound::inclusive(key))
orSome(Bound::exclusive(key))
, we can just writeBound::inclusive(key)
/Bound::exclusive(key)
.The text was updated successfully, but these errors were encountered: