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
..
EventDispatcher.h	iOS: create EventTarget when creating EventEmitter and keep it until the emitter is deallocated.	2018-06-21 14:35:39 -07:00
EventEmitter.cpp	Fabric: Getting rid of many `auto &&`	2018-06-22 07:32:49 -07:00
EventEmitter.h	iOS: create EventTarget when creating EventEmitter and keep it until the emitter is deallocated.	2018-06-21 14:35:39 -07:00
EventPrimitives.h	Fabric: Using types `EventTarget`, `EventHandler` & co. instead of `void *` everywhere	2018-05-29 15:03:57 -07:00