!!/ping everyone

@AaronMiller @Ausername @PyGamer0 @hyper-neutrino @lyxal @math @pxeger @user ^

ayo is that a lyxal voice reveal

sorta

*ignores the other 2+ already on youtube*

share this with all your friends to totally lyxalroll them

joke's on you, i do not have any friends

:(

@hyper-neutrino do we not count?

@lyxal Can I get this in a textual format?

wdym?

It's just a rickroll but by me

Oh

kekw

make the rickroll in the interpreter go there instead

Wait, you're singing "Never gonna give you up"?

mhmm

that's me

it's very e:b:ic

I also animated it too

if you can't tell, I suck at drawing

oh dw i could tell /s

jokes aside that's actually unironically pretty decent for a simple animation like that :p

+1 for actually putting effort into a rickroll for once

the best part is that I made it on mobile using one of those stop-motion animation apps

wtf

nice :P

@hyper-neutrino *lyxalroll

Please don't let this start a new age of lyxalrolling

Is it a Lyxalroll or a Lyxroll?

Or a lyroll?

Lickloll

._.

:)

@lyxal it’s a lyxlol

lickloll

@hyper-neutrino ^

yes

how does one do that

:(

:p

@lyxal I can't remember if you already gave me your verdict on this but what was your opinion on rewriting the parser (and also separating the tokenizer from it)?

I am drafting up a file structure so we can discuss the components and maybe soon start reimplementing a bit to get a workable version that can run like 1 + 2

and then see where we're at there

@hyper-neutrino I mean, I don't see much need to rewrite it

The one on main works well

@hyper-neutrino have you read the code style guide?

I outlined a list of possible files there

ah

i missed it

nice this is pretty much what i had in mind

although i would split different utility types like array, string, math, meta (e.g. all the vectorization behavior functions) although there might be too much overlap to properly do that

!!/ping everyone CMP: rewrite the parser?

Wow

CMP: rewrite the parser?

!!/hyperping

@AaronMiller @Ausername @PyGamer0 @hyper-neutrino @lyxal @math @pxeger @user ^

I don't suppose I need to give my opinion :P

I mostly want to split the tokenizer out of the parser, so if we think rewriting it is a waste of time, just splitting the file is fine for me. And even then I don't really care too much about rewriting it. It's mostly that all the digraph and string parsing behavior feels a bit... cursed.

I think someone mentioned it would be good for Vylight if there were a separate tokenizer

@hyper-neutrino there's only 2 functions at the moment

As well as a bunch of constants

There's a string grouper and the actual parser

It might be hard to split without rewriting

@lyxal whats a cmp

Chat Mini Poll

@hyper-neutrino Did someone say Ｃｕｒｓｅｄ?

aa

@AaronMiller have you checked out the code style guide?

Also, have you seen the lyxroll?

@lyxal Which code style guide would that be, again?

@AaronMiller ours

Go to the fresh beginnings branch

"documents/protocols/code guide.md"

^

@lyxal Yes. It brought tears. Interpret that however you want.

@lyxal Also, the reason that the cursed language room exists:

@AaronMiller dw I know how bad it is

@AaronMiller github.com/Vyxal/Vyxal/blob/Fresh-Beginnings/documents/…

@lyxal Oh yeah, I did read that. I then spent about half an hour figuring out how to install Black for Vim since I've never used Vim plugins.

What do you think of it? Any additions/modifications you recommend?

I think it's pretty good, though I also have no experience complying with a code style standard; I usually pretty much just write stuff and then it works and I'm happy.

So I'm maybe not the best judge

@AaronMiller neovim

But I use Vim

@AaronMiller vim; ale with black or i think official repo has a vim plugin

It does, it just took me a while to figure out how to install it

!!/hug

@lyxal ⊂((・▽・))⊃

Cute

!!/info

@PyGamer0 GitHub Repository | Online Interpreter | Tutorial | Vyxapedia | List of elements | Code Page | GitHub Organization

kek

i think this is known

I know

I just like getting a screenshot of when it happens

fair enough

Because it's happened many times actually

se chat very epic

And I always forget to screenshot it for humour purposes

@Razetime have you reviewed the code style guide yet?

no i have not

is that compulsory

also where is it

ah found it

@Razetime no, I just would appreciate your feedback

so the format for triads is also the format for n-adic right

what about variadic functions

I'm pretty sure W is the only variadic function

@Razetime pretty much

but triadic should be the highest fixed arity

hypergeometric functions needs 5 i think

but i guess 3 is good

is there any documentation standard

would comments be required anywhere

@Razetime good point.

I'll add a section on documentation

Lyxal pushed a commit to Vyxal/Fresh-Beginnings: Added a section on documentation; Feedback/Discussion needed on static typing

@VyxalBot pep8 says """ is better than '''

so we should probably use """ (dont include ''' as and option)

Come and share your opinions on static typing

!!/hyperping

@AaronMiller @Ausername @PyGamer0 @hyper-neutrino @lyxal @math @pxeger @user ^

Lyxal pushed a commit to Vyxal/Fresh-Beginnings: Update code guide.md

Lyxal pushed a commit to Vyxal/Fresh-Beginnings: forgot to update revision number

Frick

@hyper-neutrino can you 11 my pinned message to go to github.com/Vyxal/Vyxal/discussions/196

@lyxal i will say yes

hope i did it right

on mobile rn

It's good

Thank you

@lyxal iff I can be a control freak about it :þ

oh

in that case definitely yes

Hehe if you thought I was going to make the language statically typed, then you're a sussy baka

I'm still discussing code style anyway

lol

Hi

Feature requests:

- parenthesise string (like underload’s a)

- enclose string with another string - first half of other string is prepended, rest is appended.

- enumerate, when given a list of lists, appends correct number to each list

We'll add those once the rewrite is done

- flag to, if at the end of running a lambda / function / map / whatever, the current stack has more than one item, it wraps that into a list.

Oh ok

Welcome back btw!

Thx

Have you seen everything about the fresh beginnings and new code contribution protocols?

github.com/Vyxal/Vyxal/tree/Fresh-Beginnings

github.com/Vyxal/Vyxal/tree/Fresh-Beginnings/documents/…

A bit

Came back to loads of pings

Also,

github.com/Vyxal/Vyxal/discussions/191

github.com/Vyxal/Vyxal/discussions/194

github.com/Vyxal/Vyxal/discussions/196

I'll be back in a bit

Bye for now

s/bit/1.5 hours

o/

Ighto I'm back

room topic changed to Vyxal: For discussion about Vyxal. Website: github.com/Vyxal/Vyxal | Org: github.com/Vyxal | Interpreter: lyxal.pythonanywhere.com | Type !!/info for more info [chat-bot] [code-golf] [epic-gamers] [never-gonna-give-you-up] [rickroll] [unicode] [vyxal]

there was an unopened )

and it was not very nice

that moment when AUsername almost has a higher total Vyxal score than me

@Ausername It looks like the crack to your illegal string was fixed in the rollback, but this is what it was: Try it Online!

Lyxal pushed a commit to vyxapedia/main: I'm allowed to change the credits like this

@Ausername Wait, nvm I found a way to do it.

Given that only two people have sent me their emails and we haven't really gotten any progress (people are probably busy especially since university has started for lyxal again - I'm not saying we need to try to force progress but I am just making this observation), I think we should abandon Jira for now and just try to get things going in the first place.

Since things are slow I think it's unlikely we'll get unorganized quickly enough for things to go bad again, and we can decide to return to it in the future if we decide we need it, but for now, we should just discuss things here and on GitHub and try to actually get some implementing going.

@lyxal if I rewrite the tokenizer/parser would you like me to keep the output in the exact same structure?

the other idea is to have token objects that include their type and start/end position and have structure objects for things

the start/end thing is mostly in case we want more advanced error output / debugging which granted is probably unnecessary anyway

You don't need debugging if you get gud

true

actually yeah i'll just stick to the existing format just for consistency and so we can reference the old files if we need to (though ideally we shouldn't)

@PyGamer0 you electroboom fan

@lyxal what is the proper intended behavior of k`hello`H?

Related question, what is the proper intended behavior of ⁽kH?

also, should prefix modifiers be stackable (the classic example being like vv_)

ah looks like they are

@AaronMiller A lambda that pushes "hello wurld"

previously that was broken but i guess we fixed that

@hyper-neutrino yis

also: what python version are we assuming

3.7, that's what PythonAnywhere uses

aw ok

no walrusing

Walruses are ugly, stupid animals

F

G

Don't say H, don't say H, don't - argh, I can't help myself H

hyper-neutrino pushed a commit to Vyxal/hyper/parser-rewrite: add python .gitignore and start splitting parser into lexer and parser

@hyper-neutrino "k`" and then everything else parsed separate

As in, the first backtick is the digraph

@AaronMiller lambda that pushes kH

@hyper-neutrino yes they should be

@hyper-neutrino that would be great