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

Add Eq and NotEq for ListType #368

Open
nielstron opened this issue Apr 8, 2024 · 0 comments
Open

Add Eq and NotEq for ListType #368

nielstron opened this issue Apr 8, 2024 · 0 comments
Labels
bb: minor Minor issue according to bug bounty categorization bug bounty This issue is prized out as part of the Bug Bounty Program enhancement New feature or request

Comments

@nielstron
Copy link
Contributor

nielstron commented Apr 8, 2024

Is your feature request related to a problem? Please describe.
Currently list objects can not be compared directly in OpShin but only by comparing datums that contain them or by casting them into Anything. This enforces equality on a CBOR level but does not allow purely semantic comparison.

concretely compiling and executing the following does not work currently but is supposed to work

def validator(x: int, y: int):
   return [x, y] == [5, 2]

Describe the solution you'd like
An implementation of Eq and NotEq in the ListType that relies only on list semantics. Note that this execution is expensive (linear in the size of the list)

Describe alternatives you've considered
None.

Bug bounty: 200 ADA

@nielstron nielstron added the enhancement New feature or request label Apr 8, 2024
@nielstron nielstron added bug bounty This issue is prized out as part of the Bug Bounty Program bb: minor Minor issue according to bug bounty categorization labels Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bb: minor Minor issue according to bug bounty categorization bug bounty This issue is prized out as part of the Bug Bounty Program enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant