react-native/ReactCommon/fabric/core
Valentin Shergin eabf29e320 Fabric: Getting rid of many `auto &&`
Summary:
@public
After reading about move-semantic and rvalue refs I realized that we (I) definitely overuse  `auto &&` (aka universal reference) construction. Even if this is harmless, does not look good and idiomatic.
Whenever I used that from a semantical point of view I always meant  "I need an alias for this" which is actually "read-only reference" which is `const auto &`.
This is also fit good to our policy where "everything is const (immutable) by default".
Hence I change that to how it should be.

Reviewed By: fkgozali

Differential Revision: D8475637

fbshipit-source-id: 0a691ededa0e798db8ffa053bff0f400913ab7b8
2018-06-22 07:32:49 -07:00
..
componentdescriptor Fabric: Getting rid of many `auto &&` 2018-06-22 07:32:49 -07:00
events Fabric: Getting rid of many `auto &&` 2018-06-22 07:32:49 -07:00
layout Fabric: `pointScaleFactor` is now part of LayoutContext and LayoutMetrics 2018-06-22 07:32:49 -07:00
primitives Fabric: Removed unused type aliases 2018-06-01 09:37:46 -07:00
shadownode Fabric: All *EventHandlers were renamed to *EventEmitter 2018-06-09 13:16:45 -07:00
tests iOS: fix fabric core test 2018-06-09 21:52:13 -07:00
BUCK Fabric: Application layer of events infrastructure 2018-05-22 16:31:58 -07:00
conversions.h Fabric: New props treatment in `core` module 2018-05-14 16:03:49 -07:00
propsConversions.h Fabric: Getting rid of many `auto &&` 2018-06-22 07:32:49 -07:00