Improve the usability of array runtime config #3668
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #3667 and #3666 by updating the docs about the default
write_empty_chunksvalue, and adds some API toArrayandAsyncArrayso that the doc update could be done properly (i.e., without using private API).The new API on
ArrayandAsyncArrayis as follows:AsyncArray.configis public (it was private)Array.configis a new property that exposes._async_array.configAsyncArrayandArrayboth have a.with_configmethod that creates a newAsyncArray/Arraywith an updated config.This means users can now easily check the runtime configuration of an array, and get a new array (pointing to the same data) with a different configuration if they want.