Vyxal

hyper-neutrino

05:25

is vyxal.PA not working for anyone else

resizeCodeBox is not defined

firefox on debian 12

ok works on chrome

lyxal

05:40

what FF version?

hyper-neutrino

looks like it might be caused by some privacy extension or smth blocking cross site requests maybe?

loading something from unpkg failed

lyxal

works on FF 109 windows 11

hyper-neutrino

109.0 from flatpak

idk. likely just me

lyxal

+ FF 109 on android

flatpak?

@hyper-neutrino wait unpkg?

we, uh, don't use that I think

hyper-neutrino

@lyxal it's an app installer or whatever for linux

@lyxal lol what

... ok I tried again and it works now???

huh???

okay false alarm lol. i'm confused

lyxal

05:47

@hyper-neutrino oh no we do, just not for vylight

vylight used to be delivered via unpkg, but it wasn't updating straight away

so now we just get it direct from github

emanresu A

I had a similar issue before

Works now

Also why are we still using unpkg instead of jsdelivr?

lyxal

<script defer src="https://unpkg.com/react@18/umd/react.production.min.js"></script>
<script defer src="https://unpkg.com/react-dom@18/umd/react-dom.production.min.js"></script>
<script defer src="https://unpkg.com/[email protected]/dist/htm.umd.js"></script>
<script defer src="https://unpkg.com/@popperjs/core@2"></script>
<script defer src="https://unpkg.com/react-popper/dist/index.umd.js"></script>
<script defer src="https://unpkg.com/[email protected]"></script>

that's what it's used for

emanresu A

Yes, but jsdelivr is betetr

lyxal

PR it in :p

lyxal

11:22

@user okay yes

just had to change O from addVect to addElem because while it does vectorise, it handles a result of a list of strings differently

lyxal

11:54

there's something very subtly wrong with this snippet

Unrelated String

wait does scala have postfix *

what the hell does that do

lyxal

same as python

that's not the problem

Unrelated String

oh n and m are backwards

lyxal

bingo!

and that wasn't even the only place!

Unrelated String

nice

maybe you could rename the variables to have larger differences
like not rename the context variables themselves but the variables for them

maybe contextVarOne and contextVarTwo, at the cost of descriptiveness

lyxal

12:02

sure, but like what?

oh

maybe ogContextVar v3ContextVar :p

Unrelated String

or maybe the nato alphabet

contextVarMike and contextVarNovember :P

lyxal

or contextPrimary and contextSecondary

I actually like the primary/secondary names

Unrelated String

yeaj

lyxal

because n is supposed to be primary and m is supposed to be secondary semantically anyway

Unrelated String

smart

...also come to think of it which order are they supposed to be passed in

lyxal

12:06

primary then secondary if we're going by those names

Unrelated String

ah, so you're not opposed to reordering them for clarity

because i assume that m is currently passed first but if it's semantically secondary then passing it second would definitely make more sense

lyxal

pushed to github

with all 241 tests passing

thanks for the idea

very good idea

Unrelated String

yw

lyxal

#1587 is now ready for review

@user ^

lyxal

13:26

"Return a shallow copy of this grammar"

Unrelated String

damn, i was just about to write my own library for that

lyxal

"Returns True if the generator has at index"

perfect

Unrelated String

- Draws lines
- Draw a line

Vyxal Bot

22:00

Lyxal approved on PR #1587 (Vyxal/Vyxal): "An approval for merging when ready. Obviously, don't merge straight away. "

ysthakur commented on PR #1587 (Vyxal/Vyxal): "I'd approve this if I could lol"

user

22:40

@lyxal Which theme is this btw?

lyxal

Something ocean I think

I don't have my laptop rn but it's an ocean version of a theme with a longer name

I think it comes with vs code

user

Huh, searching doesn't give any useful results

Anyway, I'm a light mode heathen :P

lyxal

It was an ocean variant of a theme

I used to use pitch black with some additional beedab shades but new computer so new theme

lyxal

23:17

@user community material theme ocean high contrast

user

Thanks!

lyxal

just know that it does italicise some things

user

Yeah I'm fine with that

Oh that's a bit odd

Why is def not italicized?

lyxal

/shrug

user

Oh well, it's got colors

lyxal

23:24

dang I don't have that userscript that autoreplaces /shrug

user

🤷

lyxal

¯\_(ツ)_/¯

found it!

Oh! I also found the paste to upload userscript I used to use that actually works!

hell yeah

lyxal

23:40

@user I've resolved all the conversations on the add-tests PR. Good to merge?

user

Go ahead!

Vyxal Bot

Lyxal merged PR #1587 (Vyxal/Vyxal) (Vyxal:add-more-v3-tests → Vyxal:version-3): Add more v3 tests

Lyxal deleted branch Vyxal/add-more-v3-tests

lyxal

haha nice

user

If you use semver, Vyxal will get to v4.2.0 at some point

lyxal

we could release it now

there's already a v4 release

user

23:43

Oh yeah, no code

How do you even improve on that? I suppose you could turn the README from Markdown into a txt file

Since MD could be considered code

How do you feel about the Scala Native PR btw? Hold off on it and focus on tests, close it, merge it and maybe get rid of it later?

lyxal

@user make it a word document

user

And a .doc instead of .docx for extra cursedness

lyxal

@user if we're going to do it, we should do it now while there's still a small element base

that way, as we start adding more stuff, it can be tested as needed

user

👍

lyxal

because now that there's sufficient tests for everything done, unless there's any other infrastructure changes, we're going full steam ahead on elementing

user

23:46

Before we do that, is it possible we need to make any radical changes to how we do things?

(adding elements, interpreting, parsing, defining helpers, etc.)

Or does it look like it's safe to continue as is?

lyxal

there was the discussion about whether there should be something like addPartialVect

but that isn't too radical

I think we've covered everything radical

user

Cool

We might want to add === extension method on VAnys to turn somenum == VNum(0) into somenum === 0 and stuff

Although ScalaTest has its own === operator so not sure how that'd work

lyxal

====

4 equal signs

Vyxal Bot

Lyxal approved on PR #1588 (Vyxal/Vyxal): "I think the fact that everything has to be JS compatible means that code we write will fit just fine into the requirements of Native. As in, we won't be using anything Java anyway."

lyxal

@emanresuA now that's just excessive. We're code golfers, not code bowlers

user

23:52

somenum `== (in Vyxal, I mean)` 0

lyxal

v=

user

v_= would be a valid operator name

You need an underscore if you've got a mixed identifier

There's also =:=

lyxal

oh

oh I have the perfect thing

⩵

it's a single unicode character

== v ⩵

emanresu A

That's gonna result in confusion. Does scala allow arbitrary unicode operators anyway?

lyxal

Well duh it's gonna result in confusion. That's the whole joke ya dingus!

user

23:56

That's emanresu, not dingus

@emanresuA I don't think so. You can use backticks around them though, but they'll have the lowest precedence

Transcript for