Vyxal

Vyxal Bot

11:55

Lyxal pushed a commit to Vyxal/v3-momentum-branch-2: Implement ḃit

github-actions[bot] pushed a commit to Vyxal/v3-momentum-branch-2: Refresh element and/or trigraph docs from recent commit

Ginger

12:12

!!/status

Vyxal Bot

@Ginger I am doing a check of your search history.

Ginger

(⁠‘⁠◉⁠⌓⁠◉⁠’⁠)

Vyxal Bot

12:55

Lyxal pushed a commit to Vyxal/v3-momentum-branch-2: Implement nċr

Lyxal assigned Lyxal to pull request #1790 (Version 3 Momentum PR #2) in Vyxal/Vyxal

github-actions[bot] pushed a commit to Vyxal/v3-momentum-branch-2: Refresh element and/or trigraph docs from recent commit

Vyxal Bot

13:38

Lyxal pushed a commit to Vyxal/v3-momentum-branch-2: Add ė

lyxal

@user the literate lexer doesn't seem to be recognising single-letter keywords

like it isn't turning * into × or any other single letter alias I try

vyxal.github.io/#WyJsIiwiIiwiIiwiMyA1ICogIiwiIl0= is expected behaviour

I tried a whole lot of things like changing the definition of a word, or trying to find where the conversion could possibly be looking up the single token list first but nothing worked

Vyxal Bot

github-actions[bot] pushed a commit to Vyxal/v3-momentum-branch-2: Refresh element and/or trigraph docs from recent commit

lyxal

okay so it's definitely finding the existing symbol before looking at keywords

e.g. changing double's symbol to A, and adding d as a keyword of times makes it get recognised

user

14:37

@lyxal No I just thought all keywords started with letters: github.com/Vyxal/Vyxal/blob/v3-momentum-branch-2/shared/src/…

Or underscores

The CharIn("a-zA-Z_") ~~ at the start is ruling out *

lyxal

22:05

@user but even trying a keyword with a single letter isn't recognised

user

I'm testing rn, lemme try something

I love how making one change to the lexer causes errors in a completely unrelated area

Spooky action at a distance

lyxal

@user fwiw I tried adding * to that and it didn't change anything

user

So one minor problem was that the backslashes weren't necessary (docs), but that didn't fix it so that's not the issue

lyxal

Yeah I tried no backslashes too

I even tried making the definition of word CharsWhileIn(string, 1).! to no avail

But noticeably, when there's a keyword that's one letter that isn't an element symbol already defined it works

9 hours ago, by lyxal

e.g. changing double's symbol to A, and adding d as a keyword of times makes it get recognised

user

Yeah that's interesting

lyxal

22:19

So the problem is that one character keywords are being treated as normal symbols first instead of aliases

user

Which doesn't make sense, because the keyword parsers are listed before SBCSLexer.token in LiterateLexer's singleToken

user

22:40

So now lambda params aren't detected as params for some reason

Fun fun fun

If I ever tell you I'm going to make a new language with a new parser, please hit me with a brick

what the fuck

I swear all I added was a print statement to debug and it's working now

what in god's temporarily green earth is this fuckery

AaaaaSAAAAAAAAAAAAAAAAa

watch it not work the moment I adde a new test

what did i change

past me what did you do

TELL ME YOUR SECRETS

Tell me or I will make you pay

I will ruin your life you smug piece of shit

Holy guacamole it's still working

wut

TI'S STILL WORKING

AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

lyxal

Now you know what it's like writing tests :p

user

I must have done a deal with the devil

This is the only explanation

The devil took my soul and all memory of the deal

Yes

And since I have no soul I'm going to hell anyway, which means I can do anything I want with no consequences worse than the ones I'm already going to face

AHAHAHAHHHHAAAAAAAAAA

Time to go the local pet store and kick every puppy there

@lyxal And I only wrote one test right now, I was just testing the tests you wrote

How in the world do you stay sane?

Or do you?

Is it all just a pretense?

lyxal

Industry's best kept secret :p

user

Are you actually a deranged lunatic tping away from a psych ward

Because that's where I see myself heading at this rate

lyxal

You'll never know :p

user

22:52

@lyxal Which industry?

lyxal

@user all of them

user

:o

lyxal

I went around to every industry and forced them to sign ndas

You'd be surprised how easy it is to break into some of these places :p

Vyxal Bot

ysthakur pushed a commit to Vyxal/v3-momentum-branch-2: Allow more flexibility with what keywords can be

user

Okay it should be working now, I'm going to go relax with a nice cup of coffee and try to go to bed

Tomorrow I am going to contact my advisor to change my major to something less likely to make me go mad, like logic

Surely I won't go mad if I become a logician or mathematician, right?

I'm so dumb

The test failed

argh

I was filtering with -z, that's why I thought all of them passed

user

23:31

Ah I figured it out

The word parser was indeed working, but the elementKeyword parser didn't bother converting the literate keywords to their command versions

Past me was a real moron

Good thing I know more now

Vyxal Bot

ysthakur pushed a commit to Vyxal/v3-momentum-branch-2: Make element keyowrds actually get converted

lyxal

23:55

y'know, if I had a nickel for every time I've delegated making a lexer map words to appropriate keyword tokens to someone else this year, I'd have 2 nickels

which isn't a lot, but it's weird that it's happened twice

Transcript for