Some problems in the scheduling of microtask updates and react updates

[lsbFlying]

I read the source code and learned that the way our valtio finally implements batch updates is combined with micro-task processing, which coincides with the way I guessed when I looked at the source code at first 😄, but it seems to cause input problems. Examples are as follows:

import {proxy, useSnapshot} from "./valtio";

const s = proxy({
  text: "hello",
});

function V() {
  const { text } = useSnapshot(s);
  return (
    <input
      value={text}
      onChange={(event) => {
        s.text = event.target.value;
      }}
    />
  );
}

As a result, we seem to be able to enter only English in the input language, but we can't enter a language that is not unexpected in English. I don't know if the author has tried, or it's just a problem caused by my computer.

I'm not sure if it's deliberately designed this way, or has it discussed this problem and there are other solutions.

[dai-shi]

valtio/readme.md

Lines 221 to 234 in 7fe26c2

	#### Update synchronously
	By default, state mutations are batched before triggering re-render.
	Sometimes, we want to disable the batching.
	The known use case of this is `<input>` [#270](https://github.com/pmndrs/valtio/issues/270).
	```jsx
	function TextBox() {
	const snap = useSnapshot(state, { sync: true })
	return (
	<input value={snap.text} onChange={(e) => (state.text = e.target.value)} />
	)
	}
	```