Skip to content

Potential sub-goal: guidelines to avoid panics #158

@felix91gr

Description

@felix91gr

The more I wonder about this, the more it makes sense to me: perhaps we want to make a broad guideline, or family of guidelines, aiming towards avoiding panics.

Because panics are game-over in Safety Critical, right?

There are a good few functions and operations in core that can trigger panics. Thanks in big part however, to the Rust for Linux work, most if not all essential operations should be available in a no-panicking form. We might be able to use those as footing for this set of guidelines.

How does that sound?

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