39
you are viewing a single comment's thread
view the rest of the comments
[-] kubica@fedia.io 3 points 6 months ago

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 = ....

[-] calcopiritus@lemmy.world 9 points 6 months ago* (last edited 6 months 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.

[-] BatmanAoD@programming.dev 3 points 6 months 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.

this post was submitted on 11 Sep 2025
39 points (97.6% liked)

Rust

7922 readers
9 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

!performance@programming.dev

Credits

  • The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 2 years ago
MODERATORS