-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explicitly instantiate Table::find_first #2624
Conversation
A number of overloads of `Table::find_first` were not making it into the prebuilt core release for Node. Adding explicit instantiations ensures they do.
Please check your coverage here: https://ci.realm.io/job/realm/job/realm-core/job/PR-2624/1/Diff_Coverage |
Check the performance result here: https://ci.realm.io/job/realm/job/realm-core/job/PR-2624/1/Performance_Report |
👍 |
Check the performance result here: https://ci.realm.io/job/realm/job/realm-core/job/PR-2624/2/Performance_Report |
Please check your coverage here: https://ci.realm.io/job/realm/job/realm-core/job/PR-2624/2/Diff_Coverage |
Other explicit instantiations were added in #2624, but `BinaryData` was overlooked.
Other explicit instantiations were added in #2624, but `BinaryData` was overlooked.
Other explicit instantiations were added in #2624, but `BinaryData` was overlooked.
A number of overloads of
Table::find_first
were not making it into the prebuilt core release for Node. Adding explicit instantiations ensures they do.This is needed for realm/realm-js#1023.