Skip to content

Implicit module name duplication #7

Closed
@Emoun

Description

@Emoun

Since procedural macros will soon support hygiene, it would be appropriate to implement implicit module name duplication.

if duplicate is applied to a module, the user is currently required to make sure that the module has a unique name for every duplicate. This is tedious and must be done every time. To improve the user experience, duplicate could use hygiene to allow all duplicates to keep the same module name, but with different hygiene. This means the user no longer has to manually assign names to each module duplicate.

The rule could be that if duplicate is applied to a module directly, hygienic renaming will kick in, however, if the module is already renamed by a substitution identifier, the hygienic renaming won't happen. This should therefore be a non-breaking change.

Metadata

Metadata

Assignees

No one assigned

    Labels

    D-acceptedA decision (D) has been made and the issue will be worked onI-featureThis issue (I) regards a (potential) feature in the projectT-acceptedTriage (T): Initial review accepted issue/PR as valid

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions