News for hackers. Stuff that matters.
Re:Introducing Rust Language Server by lmm on Wednesday October 19, 2016 @09:55AM (#12743750)
I suspect I would - I'll happily guess if I can take a look at the code (or at least the signatures of "filter", "apply", "second" and "i").
Re:Introducing Rust Language Server by iopq on Thursday October 20, 2016 @12:24AM (#12749720)
`i` is just getting closed over, it's an integer

filter is from the standard lib

apply is defined as

    fn apply<A, B, C, F, G>(mut f: F, a: A) -> impl FnMut(&B) -> C
         where F: FnMut(&B) -> G,
               G: FnMut(A) -> C,
               A: Clone
    {
        move |b| f(b)(a.clone())
    }

second comes from

https://github.com/Stebalien/tool-rs/blob/master/src/sequenc... which means you have to track down its implementation somewhere in macros

Re:Introducing Rust Language Server by iopq on Thursday October 20, 2016 @02:23AM (#12750101)
I put the whole code in a separate branch for you:

https://bitbucket.org/iopq/fizzbuzz-in-rust/src/920bd2bd1267...

this doesn't work, so I want you to tell me why

Re:Introducing Rust Language Server by lmm on Thursday October 20, 2016 @07:17AM (#12751336)
Hmm fair enough, harder than I thought (I don't know Rust, the error just sounded sensible). It reads like the function you're passing into filter is supposed to be "lifetime-generic" taking a parameter whose lifetime comes from the for, but the function returned by apply has a fixed lifetime. But I can't see where it's getting the lifetime for that from, or what to do about it. I guess at that point I'd try adding an explicit lifetime to the return type of apply (or maybe an IDE could show it without having to write it)?
Re:Introducing Rust Language Server by iopq on Thursday October 20, 2016 @05:52PM (#12756509)
The problem is with the function `second` that I get from the other crate. If I replace the `second` function with my own implementation it works. But for the `second` implementation from tool.rs to work, Rust needs better higher ranked lifetime support.

It would also work with a closure, but I wrote my code this way to avoid closures in the first place (I was going for point-free style).

I basically just have to write my own function:

https://bitbucket.org/iopq/fizzbuzz-in-rust/src/58bfa4c58c80...

this compiles, but it seems kind of pointless since I can only use this particular function in my case (because of the extra levels of references)

if I could use the tool.rs version, it would automatically generate all the implementations I need using macros

Re:Introducing Rust Language Server by iopq on Sunday October 23, 2016 @09:33PM (#12776306)
Someone helped me with it:

I had to change the `apply` function to dereference as well, that way it doesn't run into the lifetime issue. It has something to do with higher ranked lifetimes (the inability to express the higher ranked lifetime)

This is the working version:

https://bitbucket.org/iopq/fizzbuzz-in-rust/src/95451868e27f...