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
Just to be clear: If you know the keys of your fields at compile time, you would be much better off using structs. Not only is it more efficient, but it also helps you to avoid issues like this.
Hello,
I was running some tests with the sample provided, and found out I can't bind a reference to a generic object without a reinterpret_cast.
Example code:
If I try to add an address like this, it works, as expected:
But I'd like to store a reference to "address" key. This is how I managed to make it work:
Is there a way to avoid reinterpret_cast?
If not, would such feature request fit in your roadmap?
Thank you in advance!
The text was updated successfully, but these errors were encountered: