You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There"s no way to reference a real unknown type from onTypeNotFound unless it isn"t in a module.
Say I want to build types for an existing type, and try for import shadow.${x} to build for type x:
If the type is found in module pack.Module.ActualType and I Context.getType on pack.Module.ActualType, the search assumes firstly ActualType is a property of pack.Module.
If I getType on pack.ActualType, there"s no way of finding which module of package pack it might be in and I don"t think there"s a way to import.
Running through every single type via metadata a-la tink_syntaxhub seems rather heavy duty (and compile times confirm) where now the onTypeNotFound mechanism exists, as above, there"s loads that can"t be inferred.
The other mechanism is onAfterTyping which requires a complete traversal of types rather than case-by-case.
There"s no way to reference a real unknown type from
onTypeNotFound
unless it isn"t in a module.Say I want to build types for an existing type, and try for
import shadow.${x}
to build for typex
:If the type is found in module
pack.Module.ActualType
and IContext.getType
onpack.Module.ActualType
, the search assumes firstlyActualType
is a property ofpack.Module
.If I
getType
onpack.ActualType
, there"s no way of finding which module of packagepack
it might be in and I don"t think there"s a way to import.Running through every single type via metadata a-la
tink_syntaxhub
seems rather heavy duty (and compile times confirm) where now theonTypeNotFound
mechanism exists, as above, there"s loads that can"t be inferred.The other mechanism is
onAfterTyping
which requires a complete traversal of types rather than case-by-case.see:
TypeLookupInconsistency.zip
The text was updated successfully, but these errors were encountered: