est31
est31
I'm doing something like: ```rust let mut cfg = gcc::Config::new(); cfg.file("../libfoo/file.c"); cfg.compile("libfoo.a"); ``` And it also works, but I noticed that it doesn't store stuff into the out directory any...
According to the README, they are never called by LLVM and thus don't have to be implemented in Rust. But why is their C implementation being compiled?
Of the [latest cargobomb run](https://cargobomb-reports.s3.amazonaws.com/stable-1.19-beta-1.20.0-beta.2/index.html) by @tomprince , the following regressions were reported without any error message: * https://cargobomb-reports.s3.amazonaws.com/stable-1.19-beta-1.20.0-beta.2/beta-2017-08-13/reg/radiant-rs-0.7.1/log.txt * https://cargobomb-reports.s3.amazonaws.com/stable-1.19-beta-1.20.0-beta.2/beta-2017-08-13/reg/pinyin-0.0.6/log.txt * https://cargobomb-reports.s3.amazonaws.com/stable-1.19-beta-1.20.0-beta.2/beta-2017-08-13/reg/ciruela-0.1.7/log.txt * https://cargobomb-reports.s3.amazonaws.com/stable-1.19-beta-1.20.0-beta.2/beta-2017-08-13/reg/ceramic-0.3.0/log.txt * https://cargobomb-reports.s3.amazonaws.com/stable-1.19-beta-1.20.0-beta.2/beta-2017-08-13/reg/bitarray-set-0.4.1/log.txt * https://cargobomb-reports.s3.amazonaws.com/stable-1.19-beta-1.20.0-beta.2/beta-2017-08-13/reg/bit-array-0.4.4/log.txt
Bash has a functionality to search in the history, triggered by the ctrl-r key combination. See also https://github.com/redox-os/ion/issues/287
https://github.com/rust-lang/cargo/issues/8002 https://github.com/rust-lang/cargo/pull/7977 The new feature resolver has turned metadata inadequate for some purposes, so --unit-graph was introduced.
Right now, Cargo.toml of the bzip2-sys crate claims `MIT/Apache-2.0` but it contains the entire source code of the bzip2 library.
Inspired by concerns voiced in [this comment](https://github.com/rust-lang/rust/issues/84419#issuecomment-826415318) that askama has a bad edit cycle because it involves recompilation each time. Ideally, to solve this, one could have a second rendering...
It should be possible to ctrl+c an ongoing bisection run to modify the script or do other things. Right now, this may leave behind corrupt tarballs (incomplete downloads) in the...
Quoting the bisect manual: > If you have a script that can tell if the current source code is good or bad, you can bisect by issuing the command: >...
rustc PR https://github.com/rust-lang/rust/pull/72342 Since the PR, rustc can be configured to emit unused crate warnings. Suggested by ehuss [here](https://github.com/rust-lang/rust/pull/72702#issuecomment-635512761).