> From: [email protected] > Subject: Rust-dev Digest, Vol 47, Issue 19 > To: [email protected] > Date: Mon, 19 May 2014 12:00:03 -0700 > > Send Rust-dev mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.mozilla.org/listinfo/rust-dev > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Rust-dev digest..." > > > Today's Topics: > > 1. Re: Needed Small-to-Medium Projects (Urban Hafner) > 2. Re: Why explicit named lifetimes? (Brian Anderson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 19 May 2014 10:01:23 +0200 > From: Urban Hafner <[email protected]> > To: Aaron DeVore <[email protected]> > Cc: [email protected] > Subject: Re: [rust-dev] Needed Small-to-Medium Projects > Message-ID: > <cahmxpnku2upy+jcdm0qxcxye7p1ddloqfyumsvhxzf0ij2l...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > You are much more altruistic than me Aaron ;) I just started my own > project<https://github.com/ujh/iomrascalai>that probably adds nothing > to the eco system. If you don't find something > to work on you could just join. I'm also a Rust newbie and so is the other > dev (although he knows more about it than me). > > Urban > > > On Sun, May 18, 2014 at 4:01 AM, Aaron DeVore <[email protected]>wrote: > > > I am currently in the process of learning Rust. A good way to do that is > > to start a small to medium size project. I want to help improve the Rust > > ecosystem in the process. Are there any specific niches that need a library > > of small to medium complexity? > > > > -Aaron DeVore > > > > _______________________________________________ > > Rust-dev mailing list > > [email protected] > > https://mail.mozilla.org/listinfo/rust-dev > > > > > > > -- > Freelancer > > Available for hire for Ruby, Ruby on Rails, and JavaScript projects > > More at http://urbanhafner.com > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > <http://mail.mozilla.org/pipermail/rust-dev/attachments/20140519/77bba042/attachment-0001.html> > > ------------------------------ > > Message: 2 > Date: Mon, 19 May 2014 11:52:08 -0700 > From: Brian Anderson <[email protected]> > To: [email protected] > Subject: Re: [rust-dev] Why explicit named lifetimes? > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 05/15/2014 09:30 PM, Tommi wrote: > > On 2014-05-16, at 7:14, Daniel Micay <[email protected]> wrote: > > > >> On 16/05/14 12:10 AM, Tommi wrote: > >>> I was just wondering, why do we have to explicitly specify the lifetimes > >>> of references returned from functions? Couldn't the compiler figure those > >>> lifetimes out by itself by analyzing the code in the function? > >> > >> Type inference is local to functions, so it couldn't do that. It would > >> be impossible to have libraries if inference needed to be global across > >> the entire program, and the errors would be *signicantly* harder to > >> understand as they would span across countless functions. > > > > I'm sorry, but for some reason I completely fail to understand your > > explanation. > > > > My thinking of how the compiler would work is that whenever it compiles a > > function, it would analyze it and in some sense "write in" the named > > lifetimes for that function. The named lifetimes would still be explicitly > > part of the signature of the function in the compiler's internal > > representation of the function, but not be visible in the source code. > > > > I believe the compiler does this anylisis when the lifetimes in a > signature are wrong - but just for the error message. It tries to > suggest lifetimes that will work, but the analysis is not foolproof and > can't be done automatically generally (idk why, ask niko). > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Rust-dev mailing list > [email protected] > https://mail.mozilla.org/listinfo/rust-dev > > > ------------------------------ > > End of Rust-dev Digest, Vol 47, Issue 19 > ****************************************
_______________________________________________ Rust-dev mailing list [email protected] https://mail.mozilla.org/listinfo/rust-dev
