Skip to content

Allow use of CGP proc macros without explicit import of prelude #40

@soareschen

Description

@soareschen

Currently, the CGP pro macros are unhygenic, and requires import of cgp::prelude::* for the expanded syntax to work. Unfortunately, there is no equivalent of $crate in the proc macro world to help us bind CGP constructs with proper module path.

We would need to figure out how to properly scope CGP constructs inside the macro expansion, so that the macros could work even if users don't import the prelude.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions