rust/tests/ui/non-copyable-void.rs

// ignore-wasm32-bare no libc to test ffi with

#![feature(rustc_private)]

extern crate libc;

fn main() {
    let x : *const Vec<isize> = &vec![1,2,3];
    let y : *const libc::c_void = x as *const libc::c_void;
    unsafe {
        let _z = (*y).clone();
        //~^ ERROR no method named `clone` found
    }
}
ci: Start running wasm32 tests on Travis This commit allocates a builder to running wasm32 tests on Travis. Not all test suites pass right now so this is starting out with just the run-pass and the libcore test suites. This'll hopefully give us a pretty broad set of coverage for integration in rustc itself as well as a somewhat broad coverage of the llvm backend itself through integration/unit tests. 2017-11-26 12:39:16 -06:00			`// ignore-wasm32-bare no libc to test ffi with`

std: Depend directly on crates.io crates Ever since we added a Cargo-based build system for the compiler the standard library has always been a little special, it's never been able to depend on crates.io crates for runtime dependencies. This has been a result of various limitations, namely that Cargo doesn't understand that crates from crates.io depend on libcore, so Cargo tries to build crates before libcore is finished. I had an idea this afternoon, however, which lifts the strategy from #52919 to directly depend on crates.io crates from the standard library. After all is said and done this removes a whopping three submodules that we need to manage! The basic idea here is that for any crate `std` depends on it adds an optional dependency on an empty crate on crates.io, in this case named `rustc-std-workspace-core`. This crate is overridden via `[patch]` in this repository to point to a local crate we write, and that has a `path` dependency on libcore. Note that all `no_std` crates also depend on `compiler_builtins`, but if we're not using submodules we can publish `compiler_builtins` to crates.io and all crates can depend on it anyway! The basic strategy then looks like: * The standard library (or some transitive dep) decides to depend on a crate `foo`. * The standard library adds ```toml [dependencies] foo = { version = "0.1", features = ['rustc-dep-of-std'] } ``` * The crate `foo` has an optional dependency on `rustc-std-workspace-core` * The crate `foo` has an optional dependency on `compiler_builtins` * The crate `foo` has a feature `rustc-dep-of-std` which activates these crates and any other necessary infrastructure in the crate. A sample commit for `dlmalloc` [turns out to be quite simple][commit]. After that all `no_std` crates should largely build "as is" and still be publishable on crates.io! Notably they should be able to continue to use stable Rust if necessary, since the `rename-dependency` feature of Cargo is soon stabilizing. As a proof of concept, this commit removes the `dlmalloc`, `libcompiler_builtins`, and `libc` submodules from this repository. Long thorns in our side these are now gone for good and we can directly depend on crates.io! It's hoped that in the long term we can bring in other crates as necessary, but for now this is largely intended to simply make it easier to manage these crates and remove submodules. This should be a transparent non-breaking change for all users, but one possible stickler is that this almost for sure breaks out-of-tree `std`-building tools like `xargo` and `cargo-xbuild`. I think it should be relatively easy to get them working, however, as all that's needed is an entry in the `[patch]` section used to build the standard library. Hopefully we can work with these tools to solve this problem! [commit]: https://github.com/alexcrichton/dlmalloc-rs/commit/28ee12db813a3b650a7c25d1c36d2c17dcb88ae3 2018-11-19 23:52:50 -06:00			`#![feature(rustc_private)]`
rustc: rework stability to be on-demand for type-directed lookup. 2016-11-10 11:08:21 -06:00
Fix fallout from std::libc separation 2014-02-26 11:58:41 -06:00			`extern crate libc;`
librustc: Stop reexporting the standard modules from prelude. 2013-05-24 21:35:29 -05:00
Make nonconstructable enums noncopyable, close #1907. 2012-04-04 21:07:52 -05:00			`fn main() {`
Changed most vec! invocations to use square braces Most of the Rust community agrees that the vec! macro is clearer when called using square brackets [] instead of regular brackets (). Most of these ocurrences are from before macros allowed using different types of brackets. There is one left unchanged in a pretty-print test, as the pretty printer still wants it to have regular brackets. 2016-10-29 16:54:04 -05:00			`let x : *const Vec<isize> = &vec![1,2,3];`
Rename all raw pointers as necessary 2014-06-25 14:47:34 -05:00			`let y : const libc::c_void = x as const libc::c_void;`
Make nonconstructable enums noncopyable, close #1907. 2012-04-04 21:07:52 -05:00			`unsafe {`
librustc: Remove all uses of "copy". 2013-07-02 14:47:32 -05:00			`let _z = (*y).clone();`
Fix ICE that occurs when an associated const is ambiguous. Also change several error messages to refer to "items" rather than "methods", since associated items that require resolution during type checking are not always methods. 2015-05-03 00:30:59 -05:00			//~^ ERROR no method named `clone` found
Make nonconstructable enums noncopyable, close #1907. 2012-04-04 21:07:52 -05:00			`}`
			`}`