Vyxal

Nitrodon

00:01

!!/run ⁽NÞ↑ - [123, 23]

lyxal

Vyxal bot can only service one room at a time

And we're waiting on hyper to change it back to here and restore full functionality

Nitrodon

so yeah, Þ↑ is bugged, and the bug is on line 2048.

user

00:22

@emanresuA chunkyyyyy can you approve this please?

emanresu A

If you stop calling me chunky, sure

user

@Nitrodon Thanks for that, do you want to submit a PR?

@emanresuA Aight imma call you chunkybanana :P

emanresu A

Oh waiit

Get rid of that debug print and I'll approve

user

Uhhh

Did not see that

@emanresuA Done

@emanresuA Why did you name yourself chunkybanana if you don't want to be called that?

emanresu A

I'm fine with it being my username but it's weird having people call me that

I should probably change it at some point

user

00:27

Alright

emanresu it is then

lyxal

pxeger: "simplifies" W

user

Thanks for merging, perhaps some of the other builtins will also work better with infinite lists now

lyxal

The test cases: recursion error

user

Yeah I think stack had a reference to itself or sth

But it could probably be fixed with something simple like temp = stack[::]; stack[:] = temp

lyxal

I doubt that

user

00:31

I don't dare commit directly on Github now without testing locally first, though, did that twice

emanresu A

Cursed idea: Infinite stack

lyxal

Assigning to stack doesn't seem to work

user

Assigning to stack[:] should

Assigning to stack doesn't work only because of scoping

hyper-neutrino

!!/status

Vyxal Bot

@hyper-neutrino I am doing amazingly.

hyper-neutrino

00:31

cool

user

I mean, um, I prefer languages where you declare variables

lyxal

!!/pls give cookie

emanresu A

@VyxalBot I missed you...

!!/hug

Vyxal Bot

@emanresuA (つ ͡° ͜ʖ ͡°)つ

lyxal

!!/sus

Vyxal Bot

00:32

@lyxal ඞ

user

lmao the creepy hug

emanresu A

!!/cookie

lyxal

Yay! Full functionality again

user

No cookie? :(

hyper-neutrino

!!/please make me a cookie

Vyxal Bot

00:32

@hyper-neutrino Here you go: 🍪

user

@emanresuA 🍪

hyper-neutrino

smh y'all don't even know how to use the command y'all requested

emanresu A

@user nomnomnomnomnom

user

@VyxalBot I challenge you to a bake-off! I betcha my cookies are better than yours

@emanresuA Are you alright with me assigning you to the infinite list issue?

imma assume you are

emanresu A

Sure

user

00:36

poggers

@lyxal Do you want to rollback pxeger's suggestion and go with your original code for W right now?

We can simplify later, it's more important to have it working right

emanresu A

Btw you did not fix the cartesian product issue

Vyxal Bot

chunkybanana reopened issue #585 (Ẋ doesn't work for infinite lists, Vyxal/Vyxal)

user

Oh I see what happened

I saw the other issue for overdot-X and thought I forgot to close it earlier

emanresu A

Oh

user

I've assigned myself, I'll do it over the weekend

emanresu A

00:39

Something like this was intended

Nitrodon

@user How do I set up a Python project?

I want to do this PR right, with tests and everything.

lyxal

@user on mobile

Rollback hard

user

@Nitrodon After cloning the Vyxal repository, you just cd into the Vyxal folder and run pytest tests to run all the tests (to install pytest, just do python -m pip install pytest)

If you modify the tests in elements.yaml, then you'll have to regenerate test_elements.py. To do that, run python documents/knowledge/processor.py. After that, you can run pytest tests again

Once you're done making all your changes, you can use black vyxal and black tests to format the vyxal and tests subfolders, respectively (black can be installed with pip install black too)

We actually have a contributing guide but it looks like it doesn't contain the steps to test and stuff itself

Nitrodon

"code of conduct" in that guide links to a 404.

user

@user (if you want to run a specific test instead of all our 300+ tests, use pytest tests -k "test_name")

@Nitrodon Whoops, gimme a minute to fix that

Vyxal Bot

00:52

cgccuser created branch Vyxal/cgccuser-patch-1

cgccuser opened PR #636 (Vyxal/Vyxal) (Vyxal:cgccuser-patch-1 → Vyxal:main): Fix link to code of conduct

user

That was my bad, I moved those files around a bit

Vyxal Bot

chunkybanana approved on PR #636 (Vyxal/Vyxal)

user

@lyxal Will do

Vyxal Bot

cgccuser merged PR #634 (Vyxal/Vyxal) (Vyxal:make-W-work-again → Vyxal:main): hopefully this makes W a little better

cgccuser deleted branch Vyxal/make-W-work-again

emanresu A

01:09

Copilot's learning Vyxal!

user

Nice, does that do anything meaningful?

Is it mapping a map lambda?

emanresu A

Yep

user

Hrm, maybe it needs to learn a little more lol

emanresu A

Should return zip([1,2,3,4], infinity)

Nitrodon

I don't actually see Þ∞ in elements.md

user

01:18

Huh, it should’ve been added when it was implemented

I’ll do tomorrow

Nitrodon

and I see W pops the entire stack now

lyxal

01:34

@Nitrodon yeah, I had a patch for that in a PR yesterday but it didn't get merged in time.

emanresu A

@Nitrodon Waiit....

Vyxal Bot

Lyxal approved on PR #636 (Vyxal/Vyxal): "Lgtm "

cgccuser merged PR #636 (Vyxal/Vyxal) (Vyxal:cgccuser-patch-1 → Vyxal:main): Fix link to code of conduct

cgccuser deleted branch Vyxal/cgccuser-patch-1

emanresu A

That should accelerate this a lot

Vyxal Bot

Lyxal opened PR #637 (Vyxal/Vyxal) (Vyxal:main → Vyxal:production): Update production (20/1/2022)

lyxal

@emanresuA I think I pushed a sneaky patch that skips even numbers in the prime check

emanresu A

01:38

You didn't need to lol

Oh wait when?

Because I linked to 2.4.1 so nothing should've changed

lyxal

Tuesday

emanresu A

Latest versioon uses sympy.nextprime(lhs)

emanresu A

04:08

Cursed idea: Have a 255-byte codepage so where we normally would tie, we score slightly less

hyper-neutrino

that's... an interesting idea

emanresu A

Everyone would hate it tho

lyxal

04:53

!!/hyperping

Vyxal Bot

@AaronMiller @AaroneousMiller @Allxy @Ausername @Milk @PyGamer0 @Wansen @astonearachnid @emanresuA @grandBagel @hyper-neutrino @math @pxeger @rues @user ^

lyxal

Come and review and merge these PRs if you please

PyGamer0

oh...ok

lyxal

Hyperpinging is way easier than requesting reviews on each individual PR

PyGamer0

i am not gonna merge; i fear i might break something

lyxal

04:56

They aren't able to be merged yet anyway

They require 2 reviews

Not just 1

It's been set up that they can only be merged after 2 approvals

PyGamer0

i know that

@emanresuA smh still no apl support

Vyxal Bot

chunkybanana created branch Vyxal/compare-lazylists

emanresu A

Woohoo are you proud of me? I finally did some code!

PyGamer0

i still didnt :(

Vyxal Bot

chunkybanana opened PR #641 (Vyxal/Vyxal) (Vyxal:compare-lazylists → Vyxal:main): Add comparisons for lazylists

emanresu A

05:01

@PyGamer0 You haven't opened ~60 issues

Vyxal Bot

PyGamer0 approved on PR #641 (Vyxal/Vyxal)

emanresu A

@lyxal What's an empty number?

Vyxal Bot

chunkybanana approved on PR #639 (Vyxal/Vyxal)

PyGamer0

!!/run ⍬

Vyxal Bot

@PyGamer0 0

chunkybanana merged PR #639 (Vyxal/Vyxal) (Vyxal:patch-T-dot → Vyxal:main): Fix an issue where `Ṫ` wasn't returning `0` for empty numbers

chunkybanana deleted branch Vyxal/patch-T-dot

PyGamer0

05:02

!!/run ⍺

Vyxal Bot

@PyGamer0 0

PyGamer0

ok makes sense

emanresu A

@hyper-neutrino Can we make it so that merging a PR and deleting a branch are only one message?

PyGamer0

how would you detect that

hyper-neutrino

i don't think that's as easy as i'd like it to be

emanresu A

05:03

Hm ok

hyper-neutrino

i couldn't figure out how to detect that the branch deletion was caused by a merge from the API return value

emanresu A

Do we need messaging on branch creation?

hyper-neutrino

¯\_(ツ)_/¯ maybe not

emanresu A

Did not expect this

Vyxal Bot

chunkybanana approved on PR #640 (Vyxal/Vyxal)

emanresu A

05:06

I've set that to automerge and I'm not going to do any more until it's merged because I'll just have to pull from main again

lyxal

@emanresuA basically, T dot being called on a single digit number

emanresu A

Oh

lyxal

@emanresuA my programming isn't that bad

emanresu A

05:49

→ 11 messages moved to Trash

lyxal

12:07

@emanresuA @AaroneousMiller we should plan a write up for the best-of 2021 most user involvement category based on the cop cracking chain we did

0

A: Best of CGCC 2021 - Now Accepting Nominations!

Most involvement in an answer/answers Repost of 2020 For an answer or multiple answers where multiple people were involved. This could be multiple people helping out a user on a single answer, or a back-and-forth between two or more answers trying to outgolf each other.

lyxal

12:19

Speaking of Best-of nominations, I'm lowkey tempted to nominate Vyxal LoTM for the meta post category

0

A: Best of CGCC 2021 - Now Accepting Nominations!

Most significant impact via Meta Meta is an important yet often overlooked portion of this site, where significant rules changes are decided, and the site becomes the most democratic. It allows people to present their visions of the site, and for others to show their agreement or disagreement, an...

because it brought a ton of people into vyxal, and caused discussions such as the flag debate (even if that's not necessarily a good thing), and created a whole kind of sub-community imo

it also impacted a lot of people's reputation too lol

(cries in -1k because bounties) (but not really crying because it was worth it)

lyxal

12:41

@VyxalBot hello

Vyxal Bot

@lyxal hello to you too!

lyxal

good beep boop

@VyxalBot hug

Vyxal Bot

@lyxal (づ｡◕‿‿◕｡)づ

lyxal

I love hugs from my favourite beep boop

Aaroneous Miller

13:33

@lyxal ye

Vyxal Bot

14:06

cgccuser approved on PR #637 (Vyxal/Vyxal)

cgccuser merged PR #637 (Vyxal/Vyxal) (Vyxal:main → Vyxal:production): Update production (20/1/2022)

user

@lyxal I don't think Redwolf and co. would look too kindly upon that

And while it did make a big impact, I think the spirit of that post is more about impacting the site rather than making an impact outside of the site (sure, we have more Vyxal users now, but the real impact was to github.com/Vyxal, not CGCC)

Vyxal Bot

cgccuser commented on PR #640 (Vyxal/Vyxal): "Has this been tested for lazylists?"

user

@lyxal @emanresuA ^

Vyxal Bot

cgccuser created branch Vyxal/patch-prefixes

cgccuser opened PR #642 (Vyxal/Vyxal) (Vyxal:patch-prefixes → Vyxal:main): Make copy of prefixes, add test

user

14:27

Do we have no builtin to find suffixes?

PyGamer0

we
have i think

its a diagraph i think

user

Which one is it?

PyGamer0

!!/info

Vyxal Bot

PyGamer0

@user cant find it

user

14:36

:(

Making one now

PyGamer0

do reverse prefixes then reverse each

@user maybe not documented, pretty sure there was a suffices

user

The suffixes method only works for strings ಠ_ಠ

PyGamer0

> do reverse prefixes then reverse each

!!/run 10r

Vyxal Bot

@PyGamer0 ⟨ 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 ⟩

PyGamer0

!!/run 10rṘKR

Vyxal Bot

14:40

@PyGamer0

⟨ ⟨ 9 ⟩ | ⟨ 8 | 9 ⟩ | ⟨ 7 | 8 | 9 ⟩ | ⟨ 6 | 7 | 8 | 9 ⟩ | ⟨ 5 | 6 | 7 | 8 | 9 ⟩ | ⟨ 4 | 5 | 6 | 7 | 8 | 9 ⟩ | ⟨ 3 | 4 | 5 | 6 | 7 | 8 | 9 ⟩ | ⟨ 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 ⟩ | ⟨ 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 ⟩ | ⟨ 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 ⟩ ⟩

PyGamer0

@user ^ is that what you want?

user

Pretty much, but reversed

PyGamer0

?

user

I mean < 9 > should be the last and <1 | 2| ... | 9 > should be the first

PyGamer0

!!/run 10rṘKṘR

Vyxal Bot

14:44

@PyGamer0

⟨ ⟨ 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 ⟩ | ⟨ 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 ⟩ | ⟨ 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 ⟩ | ⟨ 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 ⟩ | ⟨ 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 ⟩ | ⟨ 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 ⟩ | ⟨ 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 ⟩ | ⟨ 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 ⟩ | ⟨ 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 ⟩ | ⟨ 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 ⟩ ⟩

user

I've implemented it now, anyway, thanks

user

17:44

imma wait for this one to be merged before I start on the other infinite list issues

user

17:57

Hi @UnrelatedString

Unrelated String

greeting

user

Might I bother you to approve this PR?

user

19:00

@VyxalBot Danke

emanresu A

19:26

→ 26 messages moved to Trash

Vyxal Bot

cgccuser opened PR #650 (Vyxal/Vyxal) (Vyxal:fix-599 → Vyxal:main): Make ↔ *partially* work with infinite lazylists

emanresu A

I think we're doing v2.8 next week

user

@emanresuA How do you want filter and <--> to work with infinite lists?

emanresu A

Oh waiit

I just realised they can't work for two infinite lists, oops

user

P can't work for an infinite list either because it's also supposed to strip from the end

emanresu A

19:28

I added that as a note

P can strip from the start tho

user

But not the end

emanresu A

@user Did what you just do implement it for (list, lazylist)

@user That's fine

user

So you want P to only strip from the start for explicitly infinite lazylists?

It still won't work for infinite lazylists that we don't know are infinite

@emanresuA Ye

My PR for <--> also works when every element of lhs is contained in rhs

emanresu A

Hm ok

user

Of course, that's a very specific case that's basically useless to cover but ¯\_(ツ)_/¯

emanresu A

19:31

Actually might come in handy for latest challenge

@user We do know what lazylists are infinite

They can only come from Ḟ or constants

user

Really?

emanresu A

Yes actually

user

I am mildly suspicious of that claim because I haven't seen much infinite-list-tracking code to cover every possible case, but okay, it won't hurt to modify P to work for known infinite lists anyway

emanresu A

Most code doesn't need to handle infinite vs finite lazylists because the functionality's the same on both

user

Right, but are we tracking infiniteness in slices and the like?

Vyxal Bot

19:35

cgccuser created branch Vyxal/all-equal-inf

emanresu A

@user Oh true...

Vyxal Bot

cgccuser opened PR #651 (Vyxal/Vyxal) (Vyxal:all-equal-inf → Vyxal:main): Don't use len in all-equal

emanresu A

I just realised that can only sensibly return 0 or not terminate'

oops;'

user

:(

Can't solve the halting problem

emanresu A

May as well add a check though

user

19:38

Sure, it's good to cover as many cases as possible even if we can't get every single one

emanresu A

At least we're not Jelly and don't have to deal with infinite strings

user

lmao yeah

Vyxal Bot

cgccuser created branch Vyxal/ath-inf

user

Man, I love it when a previous PR has already fixed the issue I'm working on :)

Another one bites the dust :P

emanresu A

20:01

Ugh this is causing a lot of merge conflicts on test_complex.py

user

No pain, no gain

I'm just happy so many issues are being fixed

Feels good

Wait how are there 30 issues now?

I could've sworn I just fixed a bunch

emanresu A

Wait nvm

user

Hydra?

Thanks

Oh wait the nonlocal isn't needed if I put lst into the generator body :facepalm:

emanresu A

23:04

Is there a way to make precommit not fail on reformatting?

Vyxal Bot

chunkybanana merged PR #651 (Vyxal/Vyxal) (Vyxal:all-equal-inf → Vyxal:main): Don't use len in all-equal

chunkybanana deleted branch Vyxal/all-equal-inf

lyxal

@user there's a surprising amount of merge conflicts in the PRs

Protip: in future, insert tests into test complex into different locations

emanresu A

It's all tests

lyxal

By not all placing the tests at the end of the file, there's less likely to be conflicts

emanresu A

Let me merge infinite sublists first, I've got a weird conflict

lyxal

23:11

Go for it

emanresu A

→ 16 messages moved to Trash

lyxal

Can't wait to write the release notes and go through all the PRs :p

emanresu A

4 hours ago, by emanresu A

I think we're doing v2.8 next week

lyxal

@emanresuA s/next week/two days time

I do the releasing on Sunday nights

emanresu A

Uh oh...

I did an oopsie

Idk where

Oh waiit

I forgot to clone the iterable in compare

How do you clone a lazylist?

lyxal

23:20

@emanresuA -1 byte

@emanresuA deep_copy

That function exists for the pure reason of copying lists and lazylists in a lazy manner

It uses itertools.tee

Which returns a generator which is wrapped in a lazylist

user

@lyxal WeLl tHoSe mErGe CoNfLiCtS wOulDn"t HaPpeN If yOu ApPrOvEd ThEm

emanresu A

Ugh my imports aren't working

user

@lyxal Will do that next time

Vyxal Bot

chunkybanana merged PR #652 (Vyxal/Vyxal) (Vyxal:ath-inf → Vyxal:main): Add test for Ḟ with an infinite list

chunkybanana deleted branch Vyxal/ath-inf

user

Honestly the only reason there are so many merge conflicts is because I went crazy with the PRs today, it's probably not going to happen again anyway

We are at 13/22 on the "Builtins that need infinite list support" thing and there are 28 issues left \o/

Vyxal Bot

23:30

cgccuser closed issue #600 (`F` (filter) doesn't work on infinite lazylists, Vyxal/Vyxal)

lyxal

@user nah, it's just because of layout issues

user

wdym?

Oh like alphabetical order for the tests?

lyxal

Kind of

user

That would be a good thing to do

lyxal

I more meant that because all the tests were appended at the end there were multiple merge conflicts

Not that there's anything wrong with that though

user

23:32

Yeah there's not going to be multiple tests together that often in the future, we just happened to have 8 PRs today (I had a snow day and figured I'd get these issues out of the way :P)

Vyxal Bot

chunkybanana created branch Vyxal/compare-lazylists

chunkybanana opened PR #656 (Vyxal/Vyxal) (Vyxal:compare-lazylists → Vyxal:main): Fix lazylist comparison

user

Importing helpers inside LazyList? sus

emanresu A

I needed deep_copy

Vyxal Bot

cgccuser created branch Vyxal/deltas-inf

user

No I mean I expected it to not work

emanresu A

23:39

from vyxal.helpers import didn't work

user

I thought the only way to import helpers inside LazyList was to import it inside a function or the two modules would recursively import each other

emanresu A

@user that was probably why

user

@emanresuA You have two try:s somehow

There's a syntax error because of it here

emanresu A

Misresolved a merge conflict :P

user

Gotta love conflicts :|

user

23:53

For the j flag with infinite lists, what do you want jL to do? Would you like it to ignore the L flag? @emanresuA

Vyxal Bot

cgccuser created branch Vyxal/join-inf

cgccuser approved on PR #656 (Vyxal/Vyxal)

Transcript for