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
When SerializedModuleLoaderBase::findModule() finds a module but cannot open it, the method does not diagnose an error; it just goes on to the next path. This results in most platforms getting very generic errors like "unable to load standard library" when we might be able to describe the problem in more detail.
The exception to this is when we find a .swiftmodule directory which contains .swiftmodule files for other targets, but not the target we're currently compiling for. In that single case, we diagnose a specific error.
It would be nice to report these errors with more detail. For instance, the diagnostic could include notes describing each path we tried and why it was not suitable.
The text was updated successfully, but these errors were encountered:
I should rephrase this to clarify that I mean file system errors—"no such file", "directory instead of file", and "insufficient permissions" all map to the same generic error message.
Additional Detail from JIRA
md5: e5deb138ce3372e72f071161194d96b9
Issue Description:
When SerializedModuleLoaderBase::findModule() finds a module but cannot open it, the method does not diagnose an error; it just goes on to the next path. This results in most platforms getting very generic errors like "unable to load standard library" when we might be able to describe the problem in more detail.
The exception to this is when we find a .swiftmodule directory which contains .swiftmodule files for other targets, but not the target we're currently compiling for. In that single case, we diagnose a specific error.
It would be nice to report these errors with more detail. For instance, the diagnostic could include notes describing each path we tried and why it was not suitable.
The text was updated successfully, but these errors were encountered: