Since there's a bunch of stuff in trio that doesn't raise errors that trio-typing does, this would raise a bunch of warnings about eval files. But as typing in trio converges to the bar in trio-typing these errors would have to be addressed at some point sooner or later anyway.
Currently raises 60-ish errors, which mostly will just be ignored. (e.g. 35 errors in TRIO105 about expressions not being awaited ... because that's what the check tests for)
Since there's a bunch of stuff in
trio
that doesn't raise errors thattrio-typing
does, this would raise a bunch of warnings about eval files. But as typing intrio
converges to the bar intrio-typing
these errors would have to be addressed at some point sooner or later anyway. Currently raises 60-ish errors, which mostly will just be ignored. (e.g. 35 errors in TRIO105 about expressions not being awaited ... because that's what the check tests for)