Skip to content

FML must contain a macro for unreachable code. #68164

@chinmaygarde

Description

@chinmaygarde

Optionally, this must be able to accept a message such that the failing assertion can be explained if tripped. This need for this macro was brought up in this code-review.

Metadata

Metadata

Assignees

No one assigned

    Labels

    c: new featureNothing broken; request for a new capabilityengineflutter/engine related. See also e: labels.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions