Contributor
Regular ContributorThank you Roee, I'll pass on the feedback to engineering team.
Is there anything else you need from this case?
Regards,
Nurina
ContributorThank you, @Nurina .
If the engineering team does decide to make any improvements on this issue, I would love to know about it. Otherwise, I think we can close out this case.
Thanks again,
-Roee
Super ContributorContributorI too would be interested to know their specific reasons.
As I understand their response, I don't think they're even claiming that their check is required by the VHDL language standard. Rather, it seems they're regarding this is a code quality check or linting check of sorts. And hence WARNING and not ERROR, presumably. Though I would say even as a linting check it is still overzealous, given the limitations of the simplistic analysis that they're doing that causes it to issue warnings on perfectly good code.
As it pertains to the VHDL language standard, the VHDL LRM specifies only that "It is an error if execution of a function completes by any means other than the execution of a return statement." In the code example I provided, execution of the function always completes by execution of a return statement. The code example fully satisfies the requirement specified in the LRM.
If there's another relevant requirement somewhere in the LRM that I missed, I'd love to see a reference to it. I'm all for strict compliance with the LRM on all sides. And good quality code beyond that.
-Roee
