I'm trying to decide how the string compression will work

I'm thinking there will be five ways to delimit a string:

‘ would be a single character

’ would be a non-ASCII Unicode code point, between 0x80 and 0x7fff, in a format which makes it either one or two bytes

“ would be auto-terminated, based on the first character (for example, “14.28k would detect that it's a number and auto-terminate when it reaches k)

” would be a compressed string

For the compression, I think all ASCII characters will be mapped to themselves, then maybe some characters can be one byte constants for common strings and some other two byte constants can be used for dictionaries

no 2 char literals

i think that's ok

Recommended character for code page: ඞ

(that's a joke. Please don't do it)

Hmm, I guess the number 6 isn't really that important...

I'll just replace it

Hmm

That sounds pretty sus

Mmmm. ඞ looks like a nose

Also looks like Lyxal's nose, which has only one nostril

Any suggestions for control flow stuff?

Not sure if this counts as control flow, but a variant of a while loop that produces a value and uses the previous value (or list of previous values) would be super helpful for infinite sequence challenges

That sounds useful, I'll add it.

I'd recommend not having a C/JS/Java-style for loop too, since it looks like Ash will have better alternatives

Oh, and this isn't related to control flow, but you should make stacks the only data structure that Ash has. They're very useful.

A stack of empty stacks would be a number (the length represents an integer), and a stack of numbers would be a string

It would definitely work out all right and not be painful to work with.

The worrying part is I was already planning a suprisingly similar language to that

Although I decided against it because it's probably illegal

If Ash automatically outputted stacks of empty stacks as numbers and stacks of numbers as strings, I see no problem with it

@RedwolfPrograms A language where the only data structure is a stack?

Yup, but arrays rather than stacks.

But they'd have mostly stack-like operators.

> What is a stack but an array standing up?

I've got some information on the string notation Ash will use in the spreadsheet

Some of the cells are abbreviated