Some renaming and minor refactoring for NativeLibraryKind#72309
Some renaming and minor refactoring for NativeLibraryKind#72309bors merged 3 commits intorust-lang:masterfrom
NativeLibraryKind#72309Conversation
|
(rust_highfive has picked a reviewer for you, use r? to override) |
src/librustc_session/utils.rs
Outdated
There was a problem hiding this comment.
Hm I'm not sure I quite follow this comment -- when do we encounter Unspecified if dylib is the default? Or does this mean that (as I think) that currently when we encounter an unspecified library kind, we store it as unspecified, but the code treats it equivalently to Dylib?
If that's right, it seems like we might want to adjust this such that Dylib is instead something like Dylib { explicit: bool } perhaps? I'm not sure whether that's worthwhile though given how rarely we add things, but I'd be a bit concerned that over time we may not be actually treating unspecified entirely equivalently to unspecified.
NativeLibrary(Kind) -> NativeLib(Kind) NativeStatic -> StaticBundle NativeStaticNobundle -> StaticNoBundle NativeFramework -> Framework NativeRawDylib -> RawDylib NativeUnknown -> Unspecified
|
@bors r+ |
|
📌 Commit 8dbe4d9 has been approved by |
Rollup of 6 pull requests Successful merges: - rust-lang#71607 (clarify interaction of pin drop guarantee and panics) - rust-lang#72125 (remove broken link) - rust-lang#72133 (Add target thumbv7a-uwp-windows-msvc) - rust-lang#72304 (rustc_target: Avoid an inappropriate use of `post_link_objects`) - rust-lang#72309 (Some renaming and minor refactoring for `NativeLibraryKind`) - rust-lang#72438 (Enable ARM TME (Transactional Memory Extensions)) Failed merges: r? @ghost
No description provided.