Conversation
b53bfd0 to
cf0a45a
Compare
zerbina
left a comment
There was a problem hiding this comment.
This is not correct, sorry.
There being an error in the instantiation of a generic procedure is not an error with the definition. Besides, the way you use hasError here is wrong: AST must only be wrapped in a wrapper error (wrapError) when there's an nkError somewhere within, but this is not the case here.
In general, please document in the PR message what exactly you're fixing (what is the error and why did it occur), and also provide a test where you have made sure that it reproduces the failure, thanks. I don't want to have to investigate these issues myself each time.
|
by the words "not an error", here should continue iteration without marking anything ? |
Yes. Instantiations with errors are reported when they're inserted into the module AST. |
|
is that a global error? because here |
|
Oh, my bad, I misremembered. |
|
okay so here the error check is needed I guess, I also aware even similar kind of errors, they use |
|
To be clear, my original review comment still applies. |
|
okay, so this is the another case compiler continue compilation cause subsequent errors, the |
Summary
semProcAuxhasErrorcoverfixupInstantiatedSymbolsnkErrorkind that causen[bodyPos]raiseFieldDefectDetails
fixupInstantiatedSymbolsnow returnsfalseif instantiated symbol's AST isnkErrorkind during iterationNotes for Reviewers