Andrew Clark b77b12311f Call and Return components should use ReactElement (#11834) ...

* Call and Return components should use ReactElement

ReactChildFiber contains lots of branches that do the same thing for
different child types. We can unify them by having more child types be
ReactElements. This requires that the `type` and `key` fields are
sufficient to determine the identity of the child.

The main benefit is decreased file size, especially as we add more
component types, like context providers and consumers.

This updates Call and Return components to use ReactElement. Portals are
left alone for now because their identity includes the host instance.

* Move server render invariant for call and return types

* Sort ReactElement type checks by most likely

* Performance timeline should skip over call components

Don't think these were intentionally omitted from the blacklist of
component types.

I went ahead and updated getComponentName to include special types, even
though I don't think they're used anywhere right now.

* Remove surrounding brackets from internal display names

2017-12-12 15:04:40 -08:00

..

__tests__

react-rt-renderer, react-cs-renderer, react-call-return: Convert vars to let/const (#11721)

2017-11-30 21:40:12 +00:00

ReactCallReturn.js

Call and Return components should use ReactElement (#11834)

2017-12-12 15:04:40 -08:00