I hadn't taken a look at react-resizable-panels before but the library and the overview pages look fantastic!

reading up on "releasing zalgo" i get the problem but existing apis already allow you to do this easily:

```js
fn zalgo(ms, cb) {
if (ms === 0) cb();
else setTimeout(cb, ms);
}
```

Adding more ways to introduce this footgun seems bad but should we not also trust developers with perf features?

yea i could even imagine a `Result::err_into()` helper would be nice to have. All that would change is that current `action()?` would become `action().err_into()?`

Fantastic, thank you so much for fixing this

Oh that's fantastic, I'll try on Monday

Also when you do set up the react-compiler how do you know its working correctly?

I'm not sure if it is still the case but a few months ago I tried to set up the react-compiler with react-router "framework mode". There where no clear docs for this and i didn't get it to work at the time.

All this to say, with something like the above and using react-routers loader/clientLoader I personally feel `use` is actually very nice.

function Example() {
const [data, setData] = useState(() => fetchData());

return (
<>
<div>{use(data)}</div>
<button onClick={() => setData(fetchOtherData())}>Click</button>
</>
);
}

This pattern is pretty nice to get a stable promise that can be updated at whenever.

Promise.reject(1).finally(() => Promise.reject(2))

This will reject with 2