Just about every time I set up a new `Context.Provider`, I end up accidentally specifying a `values` prop rather than `value`.  While it's a minor error, generally I build the container in which the provider resides and commit it to the code base before I ever use it.  It's only later when I go to use it that I realize I did it again.  Since the `Context.Provider` seems pretty much useless without a `value` prop specified, I'd love it if there was a prop error if it is missing... especially if another prop is defined on the `Context.Provider` instead.
return <Context.Provider value={props.value} />;
      }
      ReactNoop.render(<App value={1} />);
      expect(Scheduler).toFlushWithoutYielding();
      
      ReactNoop.render(<App value={2} />);
      expect(() => expect(Scheduler).toFlushWithoutYielding()).toErrorDev(
        'calculateChangedBits: Expected the return value to be a 31-bit ' +
          'integer. Instead received: 4294967295',
      );
    });
    it('warns if multiple renderers concurrently render the same context', () => {
      spyOnDev(console, 'error');
      const Context = React.createContext(0);
      function Foo(props) {
        Scheduler.unstable_yieldValue('Foo');
        return null;
      }
      function App(props) {