Skip to content

Do We Want to Use CFG Aliases? #1615

Closed
@zicklag

Description

@zicklag

Just saw this TODO:

// TODO: It may be worth moving this cfg into a procedural macro so that it can be referenced by
// a single name instead of being copied around.
// https://gist.github.com/jakerr/231dee4a138f7a5f25148ea8f39b382e seems to work.

If it's something we want to do we can use the cfg_aliases crate to make convenient aliases for cfg checks. It's an extra dependency, but not really because it's already used in GFX and WGPU and it's just a macro_rules macro that doesn't have any dependencies itself.

I could open a PR if that helps.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-WindowingPlatform-agnostic interface layer to run your app inC-Code-QualityA section of code that is hard to understand or changeD-StraightforwardSimple bug fixes and API improvements, docs, test and examplesS-Ready-For-ImplementationThis issue is ready for an implementation PR. Go for it!

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions