There's a million rules that go into deciding the identity of a consumed property and it's insane to put them all into a single function, which nativeProp is currently doing.
A more functional, maybe applicative approach would be more suitable here. Regardless of the pattern applied, each identity operation would be broken out into discreet elements, whether those defined as closures or something else.
There's a million rules that go into deciding the identity of a consumed property and it's insane to put them all into a single function, which
nativePropis currently doing.A more functional, maybe applicative approach would be more suitable here. Regardless of the pattern applied, each identity operation would be broken out into discreet elements, whether those defined as closures or something else.