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
Surfacing this FIXME, which it would be great to fix before we get wider adoption. As far as I understand the module name is already contained in the mangled type name, not sure if the Runtime library gives access to it though.
The text was updated successfully, but these errors were encountered:
Resolves#218.
`String(describing:)` initializer applied to metatypes does not include a module name, which can cause problems if two different types with same name come from different modules.
OTOH `String(reflecting:)` does include module name, which makes these reflection strings slightly longer, but should prevent obscure issues with name collisions from happening.
Surfacing this FIXME, which it would be great to fix before we get wider adoption. As far as I understand the module name is already contained in the mangled type name, not sure if the Runtime library gives access to it though.
The text was updated successfully, but these errors were encountered: