Jesse Wilson
Jesse Wilson
Lets do this: * close() - immediate * shutdown() - deferred close
I think most of this is straightforward. https://github.com/cashapp/zipline/pull/711 But there’s still hard problems, like what to do about CoroutineEventLoop. Should having outstanding jobs prevent shutdown? Or should those be canceled?...
This came up again today. We could use the XCTest memory leak detection magic. The test should create a LazyList and bind it and confirm nothing leaks https://developer.apple.com/documentation/xcode/preventing-memory-use-regressions
Obsoleted by https://github.com/cashapp/redwood/issues/2174
I tried [this](https://stackoverflow.com/questions/46704572/git-error-encountered-7-files-that-should-have-been-pointers-but-werent) and it worked? ``` git rm --cached -r . git reset --hard ```
I’ve fixed the platform stuff. We still have a layout problem with the `Text` binding in EmojiSearch. We can fix it like so: https://github.com/cashapp/redwood/pull/2332
Our layout widgets (Column, LazyColumn etc.) should use the word `margin`, and apply this space outside the bounds of their child widgets. We may also add or support a cross-cutting...
To bridge this I think we change `ZiplineTreehouseUi.start` to accept a new service that owns the lock. For Zipline-layer efficiency and future-extensibility we could have a single `TreehouseWidgetService` interface that...
One more factor – we should not fall back to the cached manifest in development.
Decision to make: should we disable caching per-app or globally? Globally is simpler; per-app might work better.