Skip to content

Eliminate the lingering association between macro crates and plugins (internals) #22198

@kmcallister

Description

@kmcallister

After #22026 they are barely related, but the internals do not reflect this fact. This causes problems like #22197 and is generally confusing.

All we should do for a plugin is find the appropriate dylib file (which might not even be the one you'd want to link), find one metadata entry, and hand that off to the existing loading & registrar code.

Metadata

Metadata

Assignees

Labels

A-macrosArea: All kinds of macros (custom derive, macro_rules!, proc macros, ..)A-pluginsArea: compiler plugins, doc.rust-lang.org/nightly/unstable-book/language-features/plugin.htmlC-cleanupCategory: PRs that clean code up or issues documenting cleanup.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions