Jsor posted:

quote:

The 1st rule of Rust Club is: you don't talk about Rust Club.

The 2nd rule of Rust Club is: error: 1st rule does not live long enough.

error: aborting due to previous error

Bognar posted:

Found this joke on the rust subreddit and enjoyed it:

Lunixnerd posted:

Rust seems really cool and interesting but this: https://www.rust-lang.org/conduct.html is loving cancer. I hate it that this tumblr level safe-space bullshit is invading CS topics. It encourages outrage and taking offense while simultaneously discouraging being an adult and hardening the gently caress up. It also serves to minimize the contributions of people that don't have a place in the reverse hierarchy of 'privilege' that tumblr likes to go on about, sorry I'm not a disabled, mayonnaise gendered, polysexual, fartkin gypsy black woman quadriplegic, I hope my pull request gets some attention nonetheless because I'm trying to add value despite being a cis-het white male AKA literally hitler.

quote:

We are committed to providing a friendly, safe and welcoming environment for all, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, nationality, or other similar characteristic.

quote:

We interpret the term "harassment" as including the definition in the Citizen Code of Conduct;

piratepilates posted:

You've got some real problems if you read that and parse it as anything other than "be nice to people, don't be a dick"

sarehu posted:

Seriously? Online forums have had "rules" that are about "be nice to people, don't be a dick," since forever, for example, and they read a lot differently when they aren't full of dog-whistles and designed to reinforce a certain political thesis about how the world is.

sarehu posted:

Seriously? Online forums have had "rules" that are about "be nice to people, don't be a dick," since forever, for example, and they read a lot differently when they aren't full of dog-whistles and designed to reinforce a certain political thesis about how the world is.

Tarion posted:

You're not really supposed to use unwrap in 'production' code anyways.

Vanadium posted:

It's a catch expression thank you very much

gonadic io posted:

Does anybody want to critique my babby's first data structure? http://codepad.org/SG2ERyJn

There were a few things that I tried to do and failed. I know that the methods should probably be implemented in an impl with a &self parameter but I'm ignoring that for now.

Deus Rex posted:

Sure you are. Maybe not as much, or in all the same ways, as when you're hacking together a prototype, though.

gonadic io posted:

Is there a better way to get the first Some in a list of Options (and if there isn't any, return None) than this?

code:

let children : [(bool, bool, bool); 10] = ...;
let test_child : (bool, bool, bool) -> Option<Vec3<f32>> = ...;

children.into_iter()
        .map(|&(x, y, z)| test_child(x, y, z))
        .find(|x| x.is_some())
        .and_then(|x| x)

test_child is quite an expensive function so I want to calculate it lazily, i.e. only for the children that I need to. I had a look through the standard library but couldn't find anything like msum (as it's called in Haskell) or a more specialised variant in Iterator or Option's docs.

If anybody is interesting in my ongoing project, the ray casting functionality is done now. Also the file's reached 200 lines so I guess I should probably split it into modules and stuff. Any pointers or references are appreciated: https://gist.github.com/anonymous/224fcfb0e171941715a6

FamDav posted:

map is lazy though: https://doc.rust-lang.org/std/iter/trait.Iterator.html#method.map
and find is short circuiting: https://doc.rust-lang.org/std/iter/trait.Iterator.html#method.find

gonadic io posted:

What I have (map and find) works and is short-circuiting, I was just wondering if there was a cleaner solution like [].cat_maybes.head_option or something.

Jsor posted:

E: Actually, on a mostly unrelated note, can someone explain Box to me? I mean, I know what it does. It's a lot like a malloc'd pointer in C. I just can never find a place to use it because every time I try it feels like the Box type ends up infecting the return stack of the entire program.

FamDav posted:

super confused; why does

code:

        let a = [1, 2, 3];

        let doubled: Vec<i32> = a.iter()
            .map(|&x| x)
            .collect();

compile whereas

code:

        let a = [1, 2, 3];

        let doubled: Vec<i32> = a.iter()
            .collect();

fails because its trying to build a Vec<&i32>?

piratepilates posted:

Alright so I'm learning Rust again, and I'm trying to make a program that modifies images. I'm making a function that takes an image and returns a copy of that image that is grayscale, but I can't get it to compile yet.

...

Basically all hell breaks loose and I'm not sure what the compiler is expecting of me at this point. What am I missing to make this function work?

quote:

src/lib.rs:10:42: 10:52 error: no method named `dimensions` found for type `image::buffer::ImageBuffer<P, C>` in the current scope
src/lib.rs:10 let (image_x, image_y) = input_image.dimensions();
^~~~~~~~~~
src/lib.rs:10:42: 10:52 note: the method `dimensions` exists but the following trait bounds were not satisfied: `C : core::ops::Deref`

quote:

src/lib.rs:15:17: 15:27 error: attempted access of field `data` on type `&P`, but no field with that name was found
src/lib.rs:15 let r = pixel.data[0] as f32;

quote:

src/lib.rs:13:5: 20:7 error: mismatched types:
expected `image::buffer::ImageBuffer<image::color::Luma<u8>, C>`,
found `image::buffer::ImageBuffer<image::color::Luma<u8>, collections::vec::Vec<u8>>`