chain-able/src/OPTIMIZE.MD

interfaces that describe their intentions.

MERGECHAIN
- shorthands
- mergechain.get
- ignore & instanceof have the same types
- may be checking .meta twice
- BITWISE ON THE DECORATIONS
- USE NUMBERS FOR PROPS -> letters?
- maybe ease up on number regexp
- really intense would be numbers as map props, reduce to an int32 array, get props by index or more intense would be ADD THE NUMBERS & ha
- replace rollup build function
- options on dopemerge as params would be much smaller (knocks off 100kb...)
- ENSURE ONLY TO INSTANTIATE MAP WHEN ADDING

PARSE OBJ & SCHEMA FROM STR
FINISH BITWISE

AN EVENT LOG (.HISTORY) WHEN IT CHANGED, CAN BE USED IN METHOD FACTORY

EXPORT DIST/DEV/TS/ES6 ETC IN FOLDERS AT ROOT - EASIER TO DELETE, BETER TO IMPORT

DO NOT WRAP IN TRY CATCH AND EXTRA FNS IF ENCASE(FALSE)
ADD PROP TO ONVALID
FLOW VALIDATORS AUTO (like with or / and / !, but reusable)

https://github.com/reactjs/redux/blob/master/src/utils/warning.js

  ```js
  function(t) {
    return t && t.__esModule ? t.default : t
  }
  ```

no:
- function to return a new Map like cache = () => new Map()
- includes util?



- keys = Object.keys
- has own prperty
- assign
- less proto callls / super
- post build replacers?
  - just pre-pend & replace Object.create
  - could replace 33 void 0s
- meta


- merge to-test & matcher


- SHOULD ADD A CACHE WITH A MAP TO THE KEYS FOR FAST ACCESS