kubica comments on The Hidden Rules Behind Rust Functions & Closures

The Hidden Rules Behind Rust Functions & Closures (blog.cuongle.dev)

submitted 1 year ago by turbohz@programming.dev to c/rust@programming.dev

4 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] kubica@fedia.io 2 points 1 year ago (2 children)

It's quite annoying at the beginning that the errors you get make you believe that 'closure' is a type in itself, because the errors themselves quote the word as if it was some kind of type, but then you can't specify something like let f: closure = ....

hideshow 2 child comments

[–] calcopiritus@lemmy.world 7 points 1 year ago* (last edited 1 year ago)

Well, the closure has a type. Just you cannot declare it. That's why you do "impl Fn" instead. Because you know that whatever type the close is, it implements the "Fn" trait.

parent

[–] BatmanAoD@programming.dev 1 point 1 year ago

Do you have a different recommendation for how to display unnameable types in error messages? I'm sure the compiler team would consider any suggestions.

parent