Simon B.
Simon B.
In an older version of https://github.com/dai-shi/will-this-react-global-state-work-in-concurrent-rendering we had klyva included. At that time, klyva was passing all tests except this one: check with useTransition ✕ check 7: proper branching with...
![image](https://user-images.githubusercontent.com/8921/125290090-3ace7680-e320-11eb-955c-0dcda8291381.png) It took the Malmö Meetup (remote) recording where this screenful of code is explained to see why it's useful to sling around atom names as strings.
☝️ asking for a friend :) cc @kkogovsek
As discussed elsewhere, it would be awesome to mention useSelector specifically to help users. cc @kkogovsek
To capture the interest of developers, it would be beneficial if: 1. Understanding is easy. Ideally the "above the fold" view of the repo (and npm / ... flutter pub...
Untested! This assumes we have `compileSdkVersion 29` or higher. This copy method might be faster, or if noting else, less own code to maintain. I found this since the code...
I see no mention of GPU support, if it's relevant, PRs wanted, etc. Here's another ed25519 vanity generator that might be interesting to compare with: https://docs.rs/crate/nano-vanity/0.2.1
Under https://github.com/reenhanced/gitreflow#guiding-principles the image link is broken.
Hi, maybe I'm not understanding something, but is there not a `get()` that does the same as `get(x => x)`?
That's what he said (the pow developer)