@rak1507 It doesn't quite convert to 'false', but rather ⊂'false'. This allows for the lossless conversion of [false,"false",0]

@KamilaSzewczyk ?

@Razetime it says Dyalog APL Help 18.0

But the link leads to the 12.1 version

@PaulMansour right, but why not 0? chances are if you're using 'false' in JSON you'll want 0 in APL not ⊂'false'

ok, then it isn't lossless, but that's just a consequence of APL not having a separate boolean type

@rak1507 True, but it's convenient to be able to write out a JSON false value and a 0 and not to suffer the consequence of APL not having a separate boolean type. No?

@PaulMansour Not if you then have to convert the boolean value into 0/1 yourself.

interestingly, if you do ⎕JSON⍠'M' the type you get is 6, or 'No APL equivalent'

@rak1507 I thought there was a variant for importing true/false as 1/0, but I think I'm mistaken.

Can't find anything about that in the docs, but there could be. It does sound plausible

@Adám @KamilaSzewczyk they know about this issue...

@StackExchangeFeeds cool apl is alexa programming language

why does it exist?

@rak1507 Common Lisp has a similar problem. Not between false and 0, but between false and the empty list. The JSON library I'm using defaults to the "natural" way (making them equivalent), but a flag allows you to read it in a reversible way.

Clearly the same is needed in the APL case. No one solution fits all use cases.

Of course, one could make the default the reversible form, and then provide some function that converts a structure from that format to the natural one.

@EliasMårtenson yeah, I think that would be preferred, it's definitely too late to change it now because of backwards compatibility but maybe a variant option to do false true->0 1 would be good