**Do you want to request a *feature* or report a *bug*?**
Possibly a bug

**What is the current behavior?**
Repro demo: GitHub user search. 
Type one character and wait after the list is rendered - everything works correctly. Subsequent fetches work this way.
Type two characters faster than results for the first character are rendered and fallback will never go although the second request is successful. 

**If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. Your bug will get fixed much faster if we can run your code and it doesn't have dependencies other than React. Paste the link to your JSFiddle (https://jsfiddle.net/Luktwrdm/) or CodeSandbox (https://codesandbox.io/s/new) example below:**
https://codesandbox.io/s/k5v6ojz107

**What is the expected behavior?**
Suspense "resolves" with last resolved fetch and renders the list of users

**Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?**

react: 16.7.0-alpha.0
react-dom: 16.7.0-alpha.0
react-cache: 2.0.0-alpha.0
_current,
  workInProgress,
  elementType,
  updateExpirationTime,
  renderExpirationTime,
) {
  if (_current !== null) {
    
    
    
    
    _current.alternate = null;
    workInProgress.alternate = null;
    
    workInProgress.effectTag |= Placement;
  }
  const props = workInProgress.pendingProps;
  
  
  cancelWorkTimer(workInProgress);
  let Component = readLazyComponentType(elementType);
  
  workInProgress.type = Component;
  const resolvedTag = (workInProgress.tag = resolveLazyComponentTag(Component));