I don't want to brag because the functions I added are probably half broken I'm the most humblest person ever, but you can add a lot more digraphs now - foldl rows (w/ initial value for accumulator), foldl columns (w/ initial value), foldl rows (w/o initial value), foldl cols (w/o initial value), foldl any dimension (with and without initial value), all of those from the right (won't work with infinite generators obviously), and all of those but with scan instead of fold

Honestly, foldl by axis (with or without a start value) is probably a lot more useful than foldl columns

@user these will do nicely in the experimental branch too

Thank you

Glad to help :)

Okay so redwolf has a bounty for new programming languages that are interesting

We should totally nominate vE and v3 when they are released

Because technically, they'll be new languages

Speaking of which

well by the definition of flag ruling

each combination of flags is an independent language

or something like that (not really)

CMQ: when v3 is eventually released, should answer headers have Vyxal 3.x or just Vyxal?

Because I'm pretty sure it'll have to be Vyxal 3.x

how different is v3

I don't know yet

But it'll probably just end up being the experimental branch

Like unless I find that having Transformers is completely useless, I'll probably merge the two

hm, okay

yeah i think it'd make it clearer to specify it's vyxal 3.x

are changes backward compatible?

or will you have two version on your interpreter / online executor

@hyper-neutrino two versions

@hyper-neutrino no

Code page change, different overloads and presumably transformers

oh lol

okay yeah then you should clarify the language version

Hi

Got a problem again

here

Vertical mirror duplicates the item in the middle

It should be 1,2 instead of 11,22

What could be done to solve this

(Plus it will be better if vertical mirror auto reverses [s to ], custom mapping costs few more bytes)

Palindromize doesn't duplicate item in the middle

Mirror duplicates the item in the middle

That's how it generally works

So should I palindromize instead?

Palindromize fixes that issue

But does not convert [s to ]

My initial idea was to assign empty strings in place of the duplicated column using assign but it doesn't work (It seems there is no built-in for list index removal)

Custom mapping mirrors, feel free to add one which palindromises.

Btw can we please not have postfix operators - they're a parsing nightmare.

I'm beginning to understand just how complex CodeMirror is.

postfix is aesthetically superior to prefix

i can see how they might be a bit difficult to handle for a normal language with other kinds of operators but we are golfing here

@Ausername done correctly, they're actually easier to parse

If you're putting all your tokens into a list, you can just pop elements from that list

Transformers are elements that use the tokens as their stack

Oh true...

Never mind.

That's actually what I did to handle function arities / for loop variables but I never thought of it that way.

Btw I'm working on integrating Vylight into CodeMirror since by itself, it's a bit useless.

Integrate it into the interpreter

That'd be cool

(the online one)

Well once I've got a CodeMirror version up and running it's as simple as embedding the code.

I'll have to redo my parser a bit though, so see you in 2-3 hours.

Also, what should we do about single non-ascii characters in strings?

Option 1: Leave them.

Option 2: Add ~15k words to Vyxal's dictionary by making (non-ascii)(ascii) be a SCC.

(If the latter, can we add Taumatawhakatangihangakoauauotamateaturipukakapikimaungahoronukupokaiwhenuakitanatahu?)

Option 2 might be cool

Well right now it's a bit of a waste...

Syntax highlighting is fully implemented!

But here are a few things you might want to consider:

- Is the color scheme good?

- Should it be integrated in the header/footer

- We obviously want an option to toggle it, but should we start with it on or off?

@Underslash @AaronMiller @hyper-neutrino @Razetime @UnrelatedString @wasif @user @math @pxeger @AviFS @lyxal ^^^

(Sorry for the hyperping)

my only thought about it is that for something like ₁ƛ₍₃₅kF½*ṅ⟇, it mostly doesn't do anything

oh, and the map lambda colour might be a bit too light/similar to white

@Ausername yes

@Ausername start on

@Ausername apart from the lambdas, it looks good

wanna know what's cool?

3 4 +μd⋄ works in the E branch repl

and with that, I'm out for the night

see y'all tomorrow

o/

@Ausername try autogenerating for each symbol

@Ausername what's a hyperping o.O is it even better than a superping

@Ausername Keeping it on as the default would be better

err @lyxal why is "Vyxal" not a constant?

why would it need to be lol

although there are probably enough slots for it in the k-digraphs

@hyper-neutrino it's always good to have the language's name as a constant

i suppose

can somebody explain what the registry is to me?

i guessed it's like another stack

it's just a single item isn't it?

it's like a global variable that takes fewer bytes to work with

ok

@math The registry behaves pretty much the same as a variable, but with different commands to access, and you can apply commands directly to it: Example

so it's like a lambda variable?

it's just a value independent of the stack

@math I'm not really sure what you mean by that, but I'm realizing that my explanation makes it sound like the link was to an example of applying commands to the register. It's supposed to be an example of how to use the register. Here's an example of applying commands directly to it with &: Try it Online!

thanks , I understand the register now but

shoudn't your code add 6 to the register, add 9 to it, double it and push it to the stack?

i get 30 then

@math I added an explanation: Try it Online!

@AaronMiller i unerstand it now, thanks

For syntax highlighting, you might want to highlight other constants like ₇

@Underslash Ok

Will do later.

That moment when 'Liechtenstein' is in the Vyxal dictionary, but 'Nineteenth' is not

@math it's in the dictionary though