Sage Griffin

Did you ever get a chance to discuss this with some Rust people?

I called it the "standard convention", since it's what bindgen generates,

```rust let users = ...; let commits = Commit::belonging_to(&users).grouped_by(&users); let users_and_commits = users.into_iter().zip(commits); let releases = releases.load::.into_iter() .map(|release| (release.id, release)).collect::; users_and_commits.map(|(user, commits)| { let release_names = commits.iter().map(|c| releases[c.release_id].version) .collect::().join(", ");...

For future reference, you're supposed to say my name 3 times to summon me. :trollface:

Could have let Diesel do the grouping of Releases too, but it'd result in a lot of unnecessary cloning.

So -- this is an edge case that people definitely run into, but I think this is giving too much weight to it. What do you think about something shorter...

Yeah, I think everything related to current_context wants to live in another class. It'd be cool to do it in a way that exposes the enumeration more, as well. Do...

Yeah, I agree with you. I'll take a swing at it tomorrow. On Wed, May 8, 2013 at 3:30 PM, Joe Ferris [email protected] wrote: > I think I'd want to...

@jferris Do you think that the block API with find still makes sense given these changes?

> Is there more practical advice for on-going usage of this feature? I feel like I'm missing something or making it harder than necessary. You're not missing anything. This is...