8 ms·
I don't usually deal with stateful closures. In OO we often have file objects, and if you call Close() on said object, subsequent Read() invocations fail becaus
by throwaway894345 6y ago
I don't usually deal with stateful closures. In OO we often have file objects, and if you call Close() on said object, subsequent Read() invocations fail because the encapsulated state has changed. What's the closure analog for this?
- lostcolony 6y agoYou've never worked with a generator before? That's a stateful function. For throwing after a file handle is closed, something like - const read = (fileHandle) => { return () => { if io:isOpen(fileHandle) && io:hasNext(fileHandle) => { return io:readNext(fileHandle) } else if io:isOpen(fileHandle) {return undefined } else {throw "File is closed"} } }(myFile) read() read() io:close(myFile) read() //throws