Reviewed 2 of 3 files at r1, 1 of 1 files at r2, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @Arcticae, @Draggu, @orizi, and @piotmag769)

Reviewed 1 of 1 files at r3, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @Arcticae, @Draggu, and @piotmag769)

Reviewed all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @Arcticae, @Draggu, and @piotmag769)

Reviewed 2 of 3 files at r1, 1 of 1 files at r3, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @Arcticae, @Draggu, and @integraledelebesgue)

crates/cairo-lang-language-server/src/lang/inspect/defs.rs line 383 at r3 (raw file):

    let struct_member = ast::StructArgSingle::from_syntax_node(db, struct_member);

    let ast::OptionStructArgExpr::StructArgExpr(struct_member_expr) = struct_member.arg_expr(db)

OptionStructArgExpr::Empty is also a valid path here, it mean that the expression looks like this:

let my_field = 5;

MyStruct {
   my_field,
}

I think we want to handle it as well

Reviewable status: 3 of 4 files reviewed, 1 unresolved discussion (waiting on @Arcticae, @Draggu, @mkaput, and @piotmag769)

crates/cairo-lang-language-server/src/lang/inspect/defs.rs line 383 at r3 (raw file):

I changed the implementation to handle this case. However, OptionStructArgExpr::Empty doesn't have any useful functions to retrieve ExprIds etc. thus I had to change the whole implementation to match members by names. Please have a look