Skip to content

parse.expand.features also manipulates output for regular exports which arent expanded #1080

Open

Description

@TomzBench

I have a crate that does not do any cargo expand, in that i do not use macros to produce output to my header. When I have some feature guards on some items i expect to export, these items are not exported unless I enable these features under the parse.expand.features config. This is confusing because the parse.expand.features looks like it only applies to macro expansions.

Maybe parse.expand.features should be moved to parse.features and this same config can be leveraged for both expanded code and normal code?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions