Vyxal

12:20 AM

!!/prod

Vyxal Bot

vyxal-bot[bot] opened pull request #1691 (Update production (Mar 26 2023)) in Vyxal/Vyxal

Lyxal merged pull request #1691 (Update production (Mar 26 2023)) in Vyxal/Vyxal

2 hours later…

Seggan

2:12 AM

@Ginger american spelling forever

1 hour later…

3:21 AM

→ 1 unnecessary spam message moved to Trash

naffetS

3:32 AM

color
vectorize

colour bad
vectorise bad

Now is that factual and objective or is that a heavily biased opinion?

3:46 AM

American English does seem to be the standard for programming. That said, we're using British English for Vyxal.

*Australian

Rip functions

They're still a thing

They're just in digraph space

Like v3

Makes sense

Where is : implemented

4:00 AM

It's implemented in the element dictionary at the top of the file

Because it has a stack effect that isn't just pop 1 push 1, it needs a special definition

Line 94 in elements.py

    ":": (
         "top = pop(stack, 1, ctx); stack.append(deep_copy(top)); "
         "stack.append(top)",
         1,
     ),

Have you gotten around to add :£ as a 1-byte shorthand?

(Or maybe I'll try writing it myself

@jfioasd Not yet

That'll require some thinking as to what can be changed

Because backwards compatibility is a thing

So you've ran out of available 1-byte space?

We've never really had any

You know, you can make a list of bytes that are never used in any program, and then boldly make changes on these elements.

4:07 AM

We're somewhat planning that for v3. But for now, backwards compat matters more than occasionally saving a byte somewhere

(and it's not like there are any completely useless elements)

@emanresuA Or you can make a dramatic change, since it's a different version anyway.

It doesn't have to be backwards compatible

Like Ohm v2

Yeah, v3 is a completely different codebase, completely different everything

With that, what exists in v2 is more of a guideline