Observable emitting error should not cause infinite loop on Subscribe

Under certain circumstances, a <Subscribe> with a nested component that uses a hook returned from bind(), where the observable emits an error, causes an infinite loop.

In the code example below, executable here, uncommenting the throw() on line 6 results in an infinite loop with the error being swallowed. Per discussion with @voliva who investigated this further, it seems that if and only if all of these conditions apply:

The bind doesn't have a default value
The shared observable is not passed to a <Subscribe>
The observable emits the error asynchronously
The observable doesn't emit any value before emitting the error (promises can either emit a value or error)

then the error is swallowed, and the component retries getting the value again

import { defer } from "rxjs";
import { bind, Subscribe } from "@react-rxjs/core";

async function mockFetch() {
  console.log("mockFetch()");
  // throw new Error("ouch");
  return new Promise((resolve) =>
    setTimeout(() => {
      resolve(42);
    }, 1000)
  );
}

const [useSomeData] = bind(defer(mockFetch));

function SomeData() {
  const data = useSomeData();
  return <>{data}</>;
}
export default function App() {
  return (
    <Subscribe fallback="Loading...">
      <SomeData />
    </Subscribe>
  );
}

re-rxjs / react-rxjs

Observable emitting error should not cause infinite loop on Subscribe #274