Write record_with_id, which hands back a copy of src carrying the id you were given while the record the caller passed keeps every field it had.

• The type is given to you at the top of the file: typedef struct record { int id; int score; char *name; } record;. Use it, never redefine it, and leave the three fields in that order. The grading harness declares the same struct on its side, so a changed layout breaks the call.
• Return a record whose id field holds the id parameter. score and name come straight from src.
• src arrives by value, which means the copy already happened before your first statement. Writing src.id = id; and returning src is legal and leaves the caller's record untouched. A struct is not an array here: passing it copies it.
• The copy is member by member, one level deep. name is a char *, so what gets copied is the pointer, not the characters behind it. Both records end up aimed at the same buffer, and a write through one buffer is visible through the other. That shallow copy is the contract, do not duplicate the string.
• Two calls on the same record give two independent copies. Feeding a copy back in as src behaves the same way, and the name pointer keeps travelling untouched.
• name can be NULL. Carry it over as it is and never read through it.
• An id of 0, a negative id, INT_MAX, INT_MIN: all of them are ordinary values, copied in as they come. An id that already equals src.id changes nothing.
• Grademe prints the copy, then the record the caller still holds, one line each in the form label id=<id> score=<score> name=[<name>]. An empty name prints as name=[] and a NULL name prints as the bare word name=null, brackets and all gone. Some tests add a shared= line, yes or no, reporting whether the two name fields hold the same pointer.
• Your file defines the type and the function, nothing else. It prints nothing, it allocates nothing.

Write record_with_id, which hands back a copy of src carrying the id you were given while the record the caller passed keeps every field it had.

• The type is given to you at the top of the file: typedef struct record { int id; int score; char *name; } record;. Use it, never redefine it, and leave the three fields in that order. The grading harness declares the same struct on its side, so a changed layout breaks the call.
• Return a record whose id field holds the id parameter. score and name come straight from src.
• src arrives by value, which means the copy already happened before your first statement. Writing src.id = id; and returning src is legal and leaves the caller's record untouched. A struct is not an array here: passing it copies it.
• The copy is member by member, one level deep. name is a char *, so what gets copied is the pointer, not the characters behind it. Both records end up aimed at the same buffer, and a write through one buffer is visible through the other. That shallow copy is the contract, do not duplicate the string.
• Two calls on the same record give two independent copies. Feeding a copy back in as src behaves the same way, and the name pointer keeps travelling untouched.
• name can be NULL. Carry it over as it is and never read through it.
• An id of 0, a negative id, INT_MAX, INT_MIN: all of them are ordinary values, copied in as they come. An id that already equals src.id changes nothing.
• Grademe prints the copy, then the record the caller still holds, one line each in the form label id=<id> score=<score> name=[<name>]. An empty name prints as name=[] and a NULL name prints as the bare word name=null, brackets and all gone. Some tests add a shared= line, yes or no, reporting whether the two name fields hold the same pointer.
• Your file defines the type and the function, nothing else. It prints nothing, it allocates nothing.