The APL Orchard

« first day (2669 days earlier) ← previous day next day → last day (249 days later) »

Jonathan Carroll

04:36

When I saw this Exercism problem I figured it was a great fit for APL and a stencil operator exercism.org/exercises/minesweeper - so far I have this solution and I'm wondering what can be improved - the output should be spaces instead of zeroes so I just do a final @ replace at the end. I'm also bad at parentheses, so maybe some of these aren't necessary

  board←4 5 ⍴ ' * *   *    *       '
  sweep←({+/,'*'=⍵}⌺3 3)
  (' '@{0=⍵})('*'@{'*'=board})(sweep board)

Adám

04:47

@JonathanCarroll You have a mixture of types (numbers and characters) in your result, so it looks more spaced out than specified. Also, I'd do the entire job in sweep←{5⊃c←,'*'=⍵:'*' ⋄ ⊃(×⍴⍕)+/c}⌺3 3

~~Slightly longer~~ Same length, but no conditional: sweep←{⊃('*'∩5⊃c),(×⍴⍕)+/c←,'*'=⍵}⌺3 3

Jonathan Carroll

I'd have to check the tests for each language, but I'm not sure it was strictly required to be an entirely character output :-P

Cheers!

Adám

We should add APL to Exercism.

Jonathan Carroll

I'd very much love that - and would be willing to help out

10 hours later…

RubenVerg

15:20

ideas on how to make this diagram less ugly?

Marshall

16:09

S-shaped curve instead of the straight diagonal line? Putting a gap around lines at crossings so one line is visibly "on top" of the other (either one, as long as it's a consistent ordering) could also help.

RubenVerg

yeah i was talking about this in the code golf room, i changed it and now it looks like this:

like the gap idea but not good enough at svg paths to know how to do that (:

Marshall

You put a thicker white line just behind each black one.

RubenVerg

i don't think that really works because the background of the docs page isn't pure white and i don't really want to depend on knowing the color of the background of the page

i think it now looks way better than before anyways, though.

definitely clearer

Marshall

Hm, I think you can get that working with the lines in a mask element but it's not too easy.

RubenVerg

uiua makes the lines slightly transparent

not sure if i like this look with the overlaps being lighter or not

also uiua has this weird vaguely-curved-lines style choice which is weird, i think i like mine more:

Adám

16:48

@RubenVerg You don't like the BQN style seen at aplwiki.com/wiki/File:Function_compositions.png?

RubenVerg

17:17

@Adám I don't like that the arguments to a dyad aren't always to the left and right

in my system, dyads always get arguments left and right and monads always get arguments from the bottom

here's the full set

hmm, i guess the bqn style has dyad arguments slightly left and right, except for forks

mine takes up more space but it's less ambiguous

Marshall

I think I pretty much just used the same angles as slashes in the ASCII art diagrams, going back to Phrasal Forms. I never drew trains for BQN docs though. The ones in my "Tacit Techniques" talk are shaped differently but there the main idea is to emphasize the function backbone and not the arguments.

RubenVerg

17:33

yeah, i was looking through the bqn docs for inspiration but noticed there's no forks

i think the fork doc page and/or the combinators paragraph could use some diagrams

hmm, do forks count as combinators? from a mathematical pov they are but not in the apl sense of "operator that only moves its arguments and operands around without doing any operation on them"

hmm, does valences count as a combinator?

i never thought of it as one but maybe it fits the above definition

Marshall

I think I'd call a fork a combinator but not a combinator operator. Same with Left and Right.

I classify valences as a combinator. Every "combinator" is secretly two of them glued together; for valences the two sides are just very simple and also end up doing totally different things.

2 hours later…

RubenVerg

19:31