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
{{ message }}
This repository was archived by the owner on Dec 12, 2024. It is now read-only.
The problem is in demangling the nested generic type and the problem is not small, unfortunately. This sample has the type SomeModule.Query<Entity>.QueryIterator<Entity>
This problem is the generic within the nesting of names. The modeling that we have for a swift class is a module followed by all the types that it is nested within. The nesting mechanism is fairly simple: a list of names and a list of what kind of entity they are (struct, enum, protocol, class), but that model is wrong since it doesn't account for the possibility that one of the elements might be generic. So the modeling of this has to change. For future Steve, probably the best way to do this is to consider losing the SwiftClassName type entirely and build one that has a module name and a List<SwiftType> for each element. This refactoring will break a great many things, which is why I'm not touching it now.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Test case:
AlecrimCoreData.zip
Repro: unzip &
make all TOOL_LIB=/path/to/swift-o-matic
Result: https://gist.github.com/rolfbjarne/10d91414438c2af72060e0343a1bd60b
Source: https://github.com/Alecrim/AlecrimCoreData
The text was updated successfully, but these errors were encountered: