fix: update accessor resolution

Author: kgryte

lib/node_modules/@stdlib/array/pool/lib/factory.js

@@ -32,8 +32,8 @@ var setReadOnlyAccessor = require( '@stdlib/utils/define-nonenumerable-read-only
 var ctors = require( '@stdlib/array/typed-ctors' );
 var reinterpret64 = require( '@stdlib/strided/base/reinterpret-complex64' );
 var reinterpret128 = require( '@stdlib/strided/base/reinterpret-complex128' );
-var accessors = require( '@stdlib/array/base/accessors' );
-var adtype = require( '@stdlib/array/dtype' );
+var resolveGetter = require( '@stdlib/array/base/resolve-getter' );
+var resolveSetter = require( '@stdlib/array/base/resolve-setter' );
 var ARRAY_DEFAULTS = require( '@stdlib/array/defaults' );
 var format = require( '@stdlib/string/format' );
 var ArrayBuffer = require( '@stdlib/array/buffer' );
@@ -257,9 +257,9 @@ function factory( options ) {
 				out.set( arr );
 				return out;
 			}
-			// Wrap the arrays in order to account for the possibility that `arr` is a complex number array. As we don't prohibit other "unsafe" casts (e.g., providing a `Float64Array` and specifying a `dtype` of `uint8`), we don't prohibit providing a complex number array and specifying a real `dtype`. The results will probably be unexpected/gibberish, but I am not sure we should be overly pedantic in ensuring users don't do ill-advised things...
-			get = accessors( adtype( arr ) ).accessors[ 0 ];
-			set = accessors( dtype ).accessors[ 1 ];
+			// Resolve element accessors in order to account for the possibility that `arr` is a complex number array. As we don't prohibit other "unsafe" casts (e.g., providing a `Float64Array` and specifying a `dtype` of `uint8`), we don't prohibit providing a complex number array and specifying a real `dtype`. The results will probably be unexpected/gibberish, but I am not sure we should be overly pedantic in ensuring users don't do ill-advised things...
+			get = resolveGetter( arr );
+			set = resolveSetter( out );
 			for ( i = 0; i < len; i++ ) {
 				set( out, i, get( arr, i ) );
 			}