Skip to content

Get rid of FlushType::kSingle (we don't need to enum even) #36083

@iskakaushik

Description

@iskakaushik

Concurrent message loops lie outside of the task runner framework now. We don't need single flush types.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Important issues not at the top of the work listc: contributor-productivityTeam-specific productivity, code health, technical debt.engineflutter/engine related. See also e: labels.team-engineOwned by Engine teamtriaged-engineTriaged by Engine team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions