Sets functionality need for next() and hasnext() implementation

[simranbarnwal]

Hi,

Currently, the class set doesn't have any fields, and neither does it support adding parameters or returning something from it's functions (class set is not included in the type checking environment). We tried changing those yesterday but the amount of changes required is a lot and we don't want to change how the sets group are implementing their functionalities.

Can the sets group support the above so that we can add next() and hasnext() in the set.wat file. Or can they implement next() and hasnext() as they proposed in their next milestone? To implement a set iterator, we need to be unblocked on this.

Thanks! @jpolitz @yalhessi @7bw

[7bw]

Hi, sorry for the late reply. This was due to a miscommunication between the member who wrote the conflicts part with for loop and the member who wrote the next milestone. That's why we only included the interaction with your group in our conflicts doc but not in our next milestone. We will try to implement next() and hasnext() and will let you know when we finish. Thanks for bringing this up.

[7bw]

Hi, we have implemented firstItem(), next(), and hasnext() for your reference. Please see the details here: #69

[lmxtiger]

If you are not sure how to use these 3 functions, feel free to check out the relevant test cases in tests/sets.test.ts or just let us know here.