Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix for missing Copy on shader::Buffer #170

Closed
bvssvni opened this issue Dec 26, 2014 · 1 comment
Closed

Fix for missing Copy on shader::Buffer #170

bvssvni opened this issue Dec 26, 2014 · 1 comment
Labels

Comments

@bvssvni
Copy link
Member

bvssvni commented Dec 26, 2014

The end of a rather long list of errors:

src/minecraft/region.rs:147:41: 147:50 error: the trait `core::kinds::Copy` is not implemented for the type `shader::Buffer`
src/minecraft/region.rs:147             buffers: Array::from_fn(|_| Cell::new(None)),
                                                                    ^~~~~~~~~
src/minecraft/region.rs:147:41: 147:50 note: required by `core::cell::Cell<T>::new`
src/minecraft/region.rs:147             buffers: Array::from_fn(|_| Cell::new(None)),
                                                                    ^~~~~~~~~
src/main.rs:288:38: 288:43 error: type `&core::cell::Cell<core::option::Option<shader::Buffer>>` does not implement any method in scope named `get`
src/main.rs:288                         match buffer.get() {
                                                     ^~~~~
src/main.rs:296:32: 298:27 error: type `&core::cell::Cell<core::option::Option<shader::Buffer>>` does not implement any method in scope named `set`
src/main.rs:296                         buffer.set(Some(
src/main.rs:297                             renderer.create_buffer(staging_buffer.as_slice())
src/main.rs:298                         ));
error: aborting due to 98 previous errors
Could not compile `hematite`.

When trying to add a #[deriving(Copy)] on shader::Buffer it complains that buf: gfx::BufferHandle<Vertex> is not Copy.

@bvssvni
Copy link
Member Author

bvssvni commented Feb 1, 2015

This was fixed, while the current problem is related but not the same. Closing.

@bvssvni bvssvni closed this as completed Feb 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant