Weihang Lo

> I think using `--emit metadata=/path/to/libfoo-hash.rmeta` rather than `--emit metadata` at Hmm… that doesn't look too good to me. Should we track them by [`calc_rustc_outputs(…)`](https://github.com/rust-lang/cargo/blob/c7fb75640a605027ae61cbd75d52caaeb8d3ca13/src/cargo/core/compiler/build_context/target_info.rs#L516-L545) and list them in [`cx.outputs(…)`](https://github.com/rust-lang/cargo/blob/c7fb75640a605027ae61cbd75d52caaeb8d3ca13/src/cargo/core/compiler/context/mod.rs#L374-L372)?...

> For binaries the metadata is empty, but it is still useful to know when codegen starts. Yep. I meant shouldn't the codegen start at the same time of the...

Make a lot of sense. Thanks for the explanation! Unfortunately, I don't quite sure about the consequence of setting explicit `--emit` path 😞. I still feel like it should be...

mdBook uses [elasticlunr.js](https://github.com/weixsong/elasticlunr.js) for offline searching under the hood. And according to this issue https://github.com/weixsong/elasticlunr.js/issues/53, it seems that there is no plan to support searching in other languages.

What Dylan-DPC looks correct to me in both translation and opinion.

@rukai are you still interested in fixing this?

Could you elaborate more on why this needs to be strong in terms of collision resistant? The current algorithm SipHash is strong for HashDOS protection but not really a cryptographic...

Posted by @briansmith in : > From a > My understanding is that the intent here is to use a hash function to create a stable path to a particular...

SipHash doesn't need to be the only choice. What we need for source mapping is a stable hash that won't change between different platforms, endianness, bit-width, and so on.

According to the above discussion, issues should go to either rust-lang/rustc_codegen_cranelift or rust-lang/rust. I'll close this instead. Thank you.