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
quick survey of swank interfaces in order to see what could be broken out into proper portability libraries or, more optimistically, language extensions.
this is preliminary. i pretty much just went down swank.lisp looking for definterfaces. Some other portability related things are not covered yet.
Encoding/decoding
Babel
Encode a Lisp string to an octet vector of its UTF-8 encoding
Why using the `children` prop makes `React.memo()` not work
Why using the children prop makes React.memo() not work
I've recently ran into a pitfall of [React.memo()][memo] that seems generally overlooked; skimming over the top results in Google just finds it mentioned in passing in a [React issue][regit], but not in the [FAQ] or API [overview][react-api], and not in the articles that set out to explain React.memo() (at least the ones I looked at). The issue is specifically that nesting children defeats memoization, unless the children are just plain text. To give a simplified code example:
constMemoized=React.memo(({ children })=>(<div>{children}</div>));// Won't ever re-render<Memoized>bar</Memoized>// Will re-render every time; the memoization does nothing