rust-lang / rust-lang/rust

Tracking Issue for `bare_link_kind`

Open
#132,061 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-linkage C-tracking-issue I-lang-nominated I-lang-radar O-windows P-lang-drag-1 S-blocked S-waiting-on-t-lang T-compiler T-lang
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

This is spun off from RFC 1717 (rust-lang/rfcs#1717) which is already implemented for #[link(name = "...", kind = "dylib")]
The feature gate for the issue is #![feature(bare_link_kind)].

Summary

rust-lang/rfcs#1717 implemented dllimport semantics for Windows externs (see the RFC for details). That is, it tells codegen to mark an item as being imported from a DLL:

// kind is "dylib" so dllimport applied to BAR and baz
#[link(name="foo", kind="dylib")]
extern {
    static BAR: u32;
    fn baz();
}

This tracking issue is for applying dllimport without knowing the lib name. E.g.:

// the lib is supplied separately
// via a build script, the command line, an external build system or even just a separate extern block.
#[link(kind = "dylib")]
extern {
    static BAR: u32;
    fn baz();
}

Only "dylib" and "static" kinds are allowed to be used without supplying a name.

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

Steps
Unresolved Questions
Implementation history
  • #37973

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing RFC 1717 and implementation issue #131966 to understand the feature's current state. Then follow the stabilization guide links for the documentation PR, Style Guide formatting, and stabilization PR; the tracking issue is done when all listed steps are complete.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.