aboutsummaryrefslogtreecommitdiff
path: root/doc/arrayrepr.md
diff options
context:
space:
mode:
authorMarshall Lochbaum <mwlochbaum@gmail.com>2022-06-14 22:13:43 -0400
committerMarshall Lochbaum <mwlochbaum@gmail.com>2022-06-18 16:38:12 -0400
commit9b5c6783a95dc0a0048e93e6f610beaa20932191 (patch)
tree4483c6c69cb5bdeceae1d4440c5d2107ac954883 /doc/arrayrepr.md
parentfb0e65434f9e20a80a40ceb5088aea69404480f3 (diff)
Use [] instead of >⟨⟩ in a few places
Diffstat (limited to 'doc/arrayrepr.md')
-rw-r--r--doc/arrayrepr.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/arrayrepr.md b/doc/arrayrepr.md
index 9ea4aa57..e4f93948 100644
--- a/doc/arrayrepr.md
+++ b/doc/arrayrepr.md
@@ -153,6 +153,6 @@ BQN has literal notation for lists only right now. To get an array with rank oth
∘‿2 ⥊ ⟨2,3, 4,1, 0,5⟩
- > ⟨2‿3, 4‿1, 0‿5⟩
+ [2‿3, 4‿1, 0‿5]
The characters `[]` are reserved to potentially combine list notation with merging, allowing the above to be written `[2‿3, 4‿1, 0‿5]`. This would allow non-empty arrays with rank one or more to be written without a primitive, but not rank 0 or empty arrays. Since creating arrays in general would still require primitives like `<` or `⥊`, it's not clear whether this notation is worth it. General array notation is a surprisingly complicated topic; see the article about it [on the APL Wiki](https://aplwiki.com/wiki/Array_notation).