From 9b5c6783a95dc0a0048e93e6f610beaa20932191 Mon Sep 17 00:00:00 2001 From: Marshall Lochbaum Date: Tue, 14 Jun 2022 22:13:43 -0400 Subject: =?UTF-8?q?Use=20[]=20instead=20of=20>=E2=9F=A8=E2=9F=A9=20in=20a?= =?UTF-8?q?=20few=20places?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- docs/doc/arrayrepr.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/doc/arrayrepr.html') diff --git a/docs/doc/arrayrepr.html b/docs/doc/arrayrepr.html index ce74c543..6009a771 100644 --- a/docs/doc/arrayrepr.html +++ b/docs/doc/arrayrepr.html @@ -215,14 +215,14 @@

Fortunately, I find that after a reasonable period of adjustment typing ligatures instead of spaces doesn't feel strange, and reading code is improved overall by the more explicit notation. A minor note is that lists of literal numbers, where APL-style stranding is best, tend to show up more in the snippets that beginners write to test out the language than in programs even in the tens of lines. So this issue sticks out in first experiences with BQN, but will come up less later on.

Array notation?

BQN has literal notation for lists only right now. To get an array with rank other than 1, either reshape a list, or merge a list of arrays:

-↗️
    2  2,3, 4,1, 0,5
+↗️
    2  2,3, 4,1, 0,5
 ┌─     
 ╵ 2 3  
   4 1  
   0 5  
       ┘
 
-    > 23, 41, 05
+    [23, 41, 05]
 ┌─     
 ╵ 2 3  
   4 1  
-- 
cgit v1.2.3