Skip to content

Configure separate profiles for cargo run --release and cargo flamegraph #384

Description

@CodeWenjiu

My release profile contains numerous optimizations. To avoid conflicts, I’d like to use separate profiles for flamegraph generation and production builds. Is this feasible? Or is this a reasonable feature request?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions