Builtin Array example #7092
Open
Builtin Array example #7092
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Unisay
added
Do not merge
No Changelog Required
Unisay
force-pushed
the
yura/run-compiled-code
branch
4 times, most recently
from
e7bc91d to
0edc4ee
Compare
Unisay
force-pushed
the
yura/builtin-array-example
branch
from
3ce5ccf to
68761e8
Compare
Unisay
force-pushed
the
yura/run-compiled-code
branch
6 times, most recently
from
6022c7a to
310556f
Compare
Unisay
force-pushed
the
yura/run-compiled-code
branch
from
310556f to
c575c94
Compare
Unisay
force-pushed
the
yura/builtin-array-example
branch
from
68761e8 to
f4e3f38
Compare
Unisay
force-pushed
the
yura/builtin-array-example
branch
from
f4e3f38 to
0f4f5c9
Compare
Unisay
force-pushed
the
yura/builtin-array-example
branch
from
0f4f5c9 to
9c4bb4a
Compare
|
Unisay
force-pushed
the
yura/builtin-array-example
branch
from
9c4bb4a to
5c3251c
Compare
zliu41
reviewed
Jul 16, 2025
There was a problem hiding this comment.
It should be clarified that this is an upcoming feature - not usable yet. And I think it deserves more publicity than being a part of "Other Optimization Techniques".
I suggest creating a category of pages, called "Upcoming Features". Under it, add a page called "Builtin Arrays", and put the content there. You can reference it in "Other Optimization Techniques".
doc/docusaurus/docs/working-with-scripts/other-optimization-techniques.md
Outdated
Show resolved
Hide resolved
doc/docusaurus/docs/working-with-scripts/other-optimization-techniques.md
Outdated
Show resolved
Hide resolved
Create a dedicated documentation section for features under development that are not yet available for use. This provides better organization and clearer messaging about feature availability status.
Relocate BuiltinArray documentation from optimization techniques to its own dedicated page in the upcoming features section. This addresses review feedback about giving the feature more prominence and clearer status messaging. Add comprehensive guidance on when to choose arrays versus lists from the design phase, including performance characteristics and current limitations. Clarify that lookup performance is 206x better than lists but conversion costs must be considered for multiple-lookup scenarios. Include note about future plans to add arrays directly to ScriptContext to avoid conversion overhead.
Unisay
force-pushed
the
yura/builtin-array-example
branch
from
5c3251c to
9660390
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes https://github.com/IntersectMBO/plutus-private/issues/1590
Preview: https://plutus.cardano.intersectmbo.org/pr-preview/pr-7092/working-with-scripts/other-optimization-techniques#using-builtinarray-for-index-based-lookups