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 has been archived by the owner on Mar 26, 2020. It is now read-only.
I'm not sure this is expected to work, since it's not supported in the underlying languages. You can't use a list/map/set as the "key" in a map (or the element in a set which is also a kind of key). E.g. try to declare a unordered_set<vector<int>> in C++ and it'll fail in the same way, independent of Djinni.
It might be nice if Djinni ruled this out directly (thus the "enhancement" tag I put on this issue, rather than "bug"), but in general we've been a bit loose about the generator just doing what it's told to do, and relying on the compiler to flag illegal cases like this.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I found an issue related to
set
with other collections, for example,set<map<>>
or aset<map<>>
.Here are some examples:
The generated code doesn't compile.
Here is the compilation errors generated by Xcode
##**Here is the generated error by Android Studio
##**The text was updated successfully, but these errors were encountered: