Drop migration lint for Send/Sync bound in LTO backend
The closure in question does not require Send/Sync impls, so it's OK to lose them when we just capture data.0.
This commit is contained in:
parent
662daee658
commit
5e344da217
1 changed files with 2 additions and 5 deletions
|
@ -906,11 +906,8 @@ impl ThinLTOKeysMap {
|
||||||
) -> Self {
|
) -> Self {
|
||||||
let keys = iter::zip(modules, names)
|
let keys = iter::zip(modules, names)
|
||||||
.map(|(module, name)| {
|
.map(|(module, name)| {
|
||||||
let key = build_string(|rust_str| {
|
let key = build_string(|rust_str| unsafe {
|
||||||
let _ = &data;
|
llvm::LLVMRustComputeLTOCacheKey(rust_str, module.identifier, data.0);
|
||||||
unsafe {
|
|
||||||
llvm::LLVMRustComputeLTOCacheKey(rust_str, module.identifier, data.0);
|
|
||||||
}
|
|
||||||
})
|
})
|
||||||
.expect("Invalid ThinLTO module key");
|
.expect("Invalid ThinLTO module key");
|
||||||
(name.clone().into_string().unwrap(), key)
|
(name.clone().into_string().unwrap(), key)
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue