gnzlbg
gnzlbg
cc @ibabushkin - this might be relevant for rust-semverver.
The same applies to target-features.
This was submitted in https://github.com/rust-lang/compiler-builtins/pull/251 by @dvc94ch and reviewed by @japaric . I don't think we can just delete the code without providing a replacement because I recall that Debian...
@dvc94ch I'm not a lawyer and this isn't legal advice, but the problem isn't you getting sued. The problem would be if a company which has a product that uses...
Nobody is talking about plagiarism. We tell Rust users that they can compile a Rust binary and by default no GPL licensed source code will be embedded into the binary,...
> I'll submit a PR to remove it Waait! Let's wait and see what the others think. We might need to replace this code with something else, or maybe that...
> we intercept calls to an [allocator's `alloc`](https://doc.rust-lang.org/std/alloc/trait.Alloc.html#tymethod.alloc) This should intercept calls to `#[allocator]`, methods like `alloc_zeroed` (and many others) might call`calloc` instead of `malloc`, other methods call `realloc`, etc....
> am a bit puzzled by the hypothetical part about "would we a valid core constant expression and would deallocate" @RalfJung These rules are for the initialization of `constexpr` variables....
> Ok, so basically C++ avoids the issues we've talked about here by using copy constructors whenever it moves to a non-constexpr space. I'm not sure, maybe there is some...
We discussed my previous comment on Discord yesterday, and the summary is that it is 100% flawed because it assumed that this was not possible in stable Rust today: ```rust...