Maybe Bug: Scope partially ignored if scope=function appears in C function comment

[haxtibal]

Given a C source file

void bar(void) {
}

// @relation(REQ-1, scope=file)
void foo(void) {
}

StrictDoc creates a source link in REQ-1 that jumps to to foo, highlights foo lines 4-6, but is entitled "entire file". This looks a bit like mishmash of both "comment above function is a function marker" and "scope=file is a file marker" handling.

Expectation: Not sure, but IMO most comprehensible rule would be if scope= gets priority, and the marker pointed to the whole file even if it appeared in a function comment.

@adfernandes FYI, found by comparing your example to our existing C reader behavior.