Daniel Paoliello
Daniel Paoliello
> Thanks for the PR, @dpaoliello! The implementation looks good to me `:)` > > It would be great to add another test for the transitive case @petrochenkov mentions, i.e....
> As `raw-dylib` is stabilized in 1.65, should this be beta backported? I think that's a good idea - @michaelwoerister @wesleywiser ?
Trying to rely on MSVC linker to not pull in external symbols via `/OPT:REF` is not going to work - the linker tries to resolve external symbols first, then it...
FYI, I used the Windows targets as examples when filling out the `description` field in the targets, so you'll need to update the text there to:
> I think I sneaked that in before your comment, no? Ah, you did, my bad for not checking the files...
@emilio @reitermarkus Would either of you be opposed to creating a fork of this PR minus the dependency on the new `clang-sys` and associated test changes?
> Mind fixing the 'Rendered' link in the OP? https://github.com/dpaoliello/rfcs/blob/basepath/text/3529-cargo-path-bases.md :) Oops, my bad, thanks!
Creating a thread on Rust internals to discuss alternative solutions for this issue: https://internals.rust-lang.org/t/integration-with-mono-repos-via-intermediate-directories/20160
> there are security issues Can you please elaborate on this? If you are linking against a malicious import library or loading a malicious DLL, then name confusion doesn't provide...