Skip to content

Silently dropped errors in std #28

@uazu

Description

@uazu

FileDesc::drop silently drops the error if close() fails. How could we get this error out to the user code? Is there any other code that silently drops errors?

One model might be for std to keep a (short, fixed) queue of unreported errors globally. FileDesc::drop could push any error onto this queue. There could be a function for user code to call to check whether there are any pending errors to deal with, and return the error. (This maybe has some overlap with dealing with SIGINT and SIGTERM, when those are being caught.)

Any other ideas?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions