Nikola Irinchev

I'm not sure this is the best way to do it. Such a workflow would mean that tagging a release is done before the actual release is cut rather than...

I'm not sure I understand the need for all those items on the list. To be clear, the intention is to run macOS tests on the M1 runner, not build...

Yeah, building the tests on the machine is fine, but we've already built the native binaries there, so I imagine we'd only need node and whatever RN needs to build...

Yes, we don't play super nicely with nullability yet. Definitely something on our TODO list, but don't have a timeline yet.

Point of contact from Realm: @nirinchev and @LaPeste

Note that if this turns out to be difficult to fix, we can also just prioritize platform networking for data and get rid of our custom networking implementation altogether.

The idiosyncratic .NET approach would be to use `INotifyCollectionChanged` with combination of `INotifyPropertyChanged` - your adapter is concerned only with added/removed objects, and the cells themselves subscribe for object notifications...

I guess "refresh" here is probably misleading terminology - a more precise name would probably be `notify_when_advanced_to_latest` or something similar. I would still rather see that functionality built into Core...

That doesn't match my understanding of @tgoyne's proposal. As far as I can tell, the thread where this is invoked should be thread on which the Realm is opened. So...

Just to be clear - this is not implemented, right? It's exposed in the C API, but consumers of the C++ API will need to implement it themselves using the...