Fix Iterator / Iterable confusion.

Turns out that Map values() and entries() return an object
which is both an Iterator *and* an iterable!

Author: mstange

src/test/unit/path.test.ts

@@ -107,11 +107,9 @@ describe('PathSet', function () {
   it('implements iterable, .values, .entries', function () {
     const set = new PathSet(sampleValues);
     expect(Array.from(set)).toEqual(sampleValues);
-    // @ts-expect-error The TypeScript definition of Array.from only accepts Iterable, not Iterator - not sure what's correct here
-    expect(Array.from<CallNodePath>(set.values())).toEqual(sampleValues);
+    expect(Array.from(set.values())).toEqual(sampleValues);
 
     const expectedEntries = sampleValues.map((val) => [val, val]);
-    // @ts-expect-error The TypeScript definition of Array.from only accepts Iterable, not Iterator - not sure what's correct here
     expect(Array.from(set.entries())).toEqual(expectedEntries);
   });
 });

src/utils/path.ts

@@ -83,11 +83,11 @@ export class PathSet implements Iterable<CallNodePath> {
     return this._table.delete(hashPath(path));
   }
 
-  *values(): Iterator<CallNodePath> {
+  *values(): IterableIterator<CallNodePath> {
     yield* this._table.values();
   }
 
-  *entries(): Iterator<[CallNodePath, CallNodePath]> {
+  *entries(): IterableIterator<[CallNodePath, CallNodePath]> {
     for (const entry of this) {
       yield [entry, entry];
     }