Open supersteves opened 7 years ago
Is TypeCheck.INEXISTENT_PROPERTY an OTI-specific error? Is TypeCheck itself OTI specific?
Yes and yes.
The NTI-equivalent warning is here.
Great. Thanks for clarifying so quickly. I can now disregard all TypeCheck diag groups as OTI when compiling NTI-ready parts of my code.
I think there's a bug here. When NTI runs, some OTI logic is being disabled, which should not be the case when setReportOTIErrorsUnderNTI(true)
. I'm getting this OTI error only when NTI is also enabled, when only OTI passes are done, I don't get the error.
Since updating (I was previously using a mid-summer build), I'm getting
JSC_INEXISTENT_PROPERTY
for subsequent access to properties defined in a class constructor.It only occurs in NTI when
options.setReportOTIErrorsUnderNTI(true)
. An obscure option, I know, also one I added myself, and admittedly I'm probably the only one using it.Without NTI, the error does not occur. With NTI and
options.setReportOTIErrorsUnderNTI(false)
the error does not occur. Only with NTI andoptions.setReportOTIErrorsUnderNTI(true)
does the error occur.Externs:
Class:
Warning:
Is
TypeCheck.INEXISTENT_PROPERTY
an OTI-specific error? IsTypeCheck
itself OTI specific? I didn't think it was. If it is, I just need to filter out the warning. If not, it's possibly a bug.