Opened 6 years ago

Closed 5 years ago

#342 closed defect (wontfix)

Have READ-BYTEVECTOR(!) return 0 at EOF

Reported by: cowan Owned by: alexshinn
Priority: major Milestone:
Component: WG1 - Core Keywords:


Currently, read-bytevector and read-bytevector! return an EOF object at EOF; otherwise, the number of bytes read is returned. Returning 0 at EOF instead would make the result always an exact integer. The only ambiguity would be that reading a bytevector of length 0 (which is to say, not reading any bytes at all) would not report EOF; however, this is a pointless thing to do.

Change History (2)

comment:1 Changed 5 years ago by cowan

  • Status changed from new to decided

The WG voted to reject this proposal.

comment:2 Changed 5 years ago by cowan

  • Resolution set to wontfix
  • Status changed from decided to closed
Note: See TracTickets for help on using tickets.