Unrelated to the PRs that are open, but should we do a main repo branch pruning?

Because there's a few branches there that I don't know if we need any more

make the bot do it

@lyxal yes plz

I've also pushed some refactoring work on the ctx chaining

ysthakur opened pull request #1639 ((v3) Add docs on Mill and stuff) in Vyxal/Vyxal

Just "protecting" that branch by attaching a PR to it

Do we need the antlr branch anymore? idk how easy it is to parse a grammar like Vyxal's using an ANTLR-generated parser (it's definitely possible, just might be a bit hard)

This branch for fixing R seems abandoned, does it need to be updated and PRed? Or has the issue been fixed, in which case we can delete it?

ysthakur deleted branch test in Vyxal/Vyxal

nvm

ysthakur deleted branch fix-a-little-issue-with-R in Vyxal/Vyxal

hyper made some important element evaluations in one branch, so we can't delete it yet, but we could make it an issue and then delete it

ysthakur deleted branch modified-full-stack in Vyxal/Vyxal

vdb seems very useful, can we merge it into main?

@hyper-neutrino If it's not too much trouble, could you make an issue with the contents from your element evaluations here? Then we could delete the hyper/element-evlauations branch and continue discussion on that issue (you can ignore the issue if you like, it'd just be nice to have you be the author of that issue instead of one of us posting what you wrote)

ysthakur deleted branch v3-planning-documents in Vyxal/Vyxal

I love destruction

Slightly tempted to delete all the branches there

I'll satisfy myself with burning down my own old repos

ysthakur deleted branch deepsource-config-70c34f3a in Vyxal/Vyxal

ysthakur deleted branch 1270-add-a-nice-repr-to-lazylists in Vyxal/Vyxal

@Ginger Safe to delete this? Looks like there's no changes

@user yup

ysthakur deleted branch make-vyxal-work-with-3.11 in Vyxal/Vyxal

ysthakur deleted branch add-crosshatch-dependency in Vyxal/Vyxal

poggers

Is it possible to make it so all branches with open PRs are protected? To prevent accidental deletion

lemme check

@user doesn't look like it

just have the bot auto-restore it and send you a biting rebuke in chat :p

Honestly not a bad idea

how /srs are you

I think I'll try making a userscript so it'll work with any repo though

@Ginger Like 70%

I'm not sure having the bot do it is a good idea but I really want that feature

Rather than having the bot auto-restore it, I'd prefer to have some sort of confirmation thing ("Are you sure you want to delete this branch? There is a PR associated with it")

that can probably be done

@hyper-neutrino we have a situation

We do?

that there removed message contains some spicy data that needs to be wiped from the face of the earth

Did you edit it first?

yes, this is the second time I have done this in as many weeks

no, I did not edit it

yes, I am stupid

It's fine, one's first reaction is to delete sensitive info

me when on-call mods don't show up

Well, I guess the mods'll think it's not fine, but it's perfectly understandable

please do not look at that message user

I looked at it when you posted it lol

uh

Don't worry, I don't even know what it was and it's out of my goldfish memory

I guess try and forgor it

@Ginger Just mod flag it

ok cool

@user already did

Oh well

@user I don't think so

@Ginger Just FYI: Editing prior to deletion does help a bit, because

⠀⠀A) The userscripts that make it trivial to see deleted chat messages only show the most recent revision, so the edit makes it so the text isn't as easily available to those with access and who are running an appropriate userscript. However, all revisions are still available to both room owners and moderators with a couple of clicks, unless a moderator purges the message history.

⠀⠀B) there's no stock UI way to edit to redact the content after the message has been deleted. Just purging the message history won't remove the current content, so an edit is needed.

Without a userscript, it's non-trivial to redact if the message wasn't edited prior to deletion, but there are at least two userscripts which moderators can use to edit to redact, delete, and purge the history, and can do so even if the message has been deleted. So, with one of those userscripts it's trivial to do everything that's needed regardless of if the message has been edited or deleted.

So, editing prior to deleting helps, but isn't necessary.

@VyxalBot ah dang I actually needed that

There were a few things on that branch that were useful

Hopefully the internet archive has a copy

@lyxal Cool, I will extinguish it

@lyxal Oh crap

I even hit that PR-making button to compare v3-planning-documents to version-3, and it said there weren't any changes

Mostly just a list of things that can be overloads and modifiers

Sorry, no more branch-murdering sprees, I'll consult before chopping down branches next time

ysthakur deleted branch antlr in Vyxal/Vyxal

github.com/Vyxal/Vyxal/blob/v3-planning-documents/…

That's the file I want to find

@user actually no it doesn't matter

carry on with the spree

forks maintain branches

github.com/scala-steward/Vyxal

that PR spamwall wasn't just an annoyance after all :p

Thank frick

Internet Archive didn't have it :|

Bless you, you mechanical rat butler thing

there we go

all placed onto the docs branch

yay.

@user even a fork on your other github account has the branch lol

github.com/cgccuser/Vyxal/tree/v3-planning-documents

Nice lol

I feel like I should start using it again

finally a use for all these forks

I wasn't expecting to be back so long, which is why I just went ahead using my main account

But maybe it's fine to make my profile public and display Vyxal there, since it is an impressive project even if it's an esolang

Hopefully people won't take that as a negative

If you know how to spin things, they'll see it as a positive

@lyxal Time to make a bot that continually makes new GitHub accounts that fork Vyxal/Vyxal to take snapshots :P

Man, me 2 years ago was so immature

@user it's all in the abstraction when you tell people about it. Instead of saying "here's a project I contribute to and sometimes we act a bit goofy", you say "here's a project with contributors from all over the world and I'm basically the vice president of the project"

Actually, no, me 1 day ago. What was that guy thinking?

@lyxal I get to be President of Vices? Holy frick, this is awesome

Can we have some coke and drink?

And blackjack and hookers, of course

not that kind of vice president, you bingus

the kind where you're second in command of the whole operation :p

I think I prefer the first one, thank you very much :P

By the way, are there any more future v3 features we need to start planning for right now?

Ones that may not be implemented anytime soon but still need the framework structured in a particular way

I don't think so

@lyxal unless you choose to only fork the main branch, which is common

thanks scala

Do .toMap

Unlike Kotlin, mutable maps don't inherit from the immutable Map class

Which lets implementers use a more efficient implementation for the immutable one, but has ^^^^ as a disadvantage

@user I have done the refactoring of context chaining like you suggested

!!/status

@lyxal I am doing things like creating a new type of transportation that runs on rainbows and sunshine

!!/info

@Niko GitHub Repository | Online Interpreter | Tutorial | Vyxapedia | List of elements | GitHub Organization

!!/helpme

Sorry Niko, I'm afraid I can't do that.

:(

PRs #1637 and #1638 are ready for proper reviews

@mathcat how goes progress on #1633? Do you need any help?

I tried to implement the function with python lists day before yesterday and then kinda forgor 💀.

I'm not good at keeping track at stuff, sorry.

all good - just wanted to know if you'd written anything

because I may or may not have a fix ready to push to a branch

@lyxal It's probably either two-line edit or a rewrite.

8 line edit :p

at least, that's what I came up with

wait you fixed it already?

there's a very high chance you'll come up with something better

let the code battles begin

up to you whether you still want to give it a go

I strongly suggest you do

well I'll try

there's just a backup plan iff things go not as planned

@user #887 actually

Wasn't there a discussion about this too?

Maybe

#551

also @emanresuA does PR #1535 close issue #1533?

@mathcat oh yeah that

I thought you meant discussion on #887 lol

@user string compression

@mathcat seems pretty straightforward

I'l get it done in about an hour

(if you don't want to push yours lol)

@lyxal and I can call myself "chief of automation"

@mathcat :+1:

GingerIndustries requested Lyxal's review on #24 (README more closely next time)

Lyxal approved #24 (README more closely next time): "";

GingerIndustries merged pull request #24 (README more closely next time) in Vyxal/Crosshatch

GingerIndustries deleted branch fix-readme in Vyxal/Crosshatch

yourstack.goofy

goofy.aaa

that's a valid domain name lmao

@lyxal uh what would prevent vyxal from doing:

def index_indices_or_cycle(lhs, rhs):
    prevs = []

    def gen():
        curr = lhs
        first = True
        while True:
            curr = rhs(curr)
            print(curr)
            # if curr == lhs and not first:
            #     break
            if curr in prevs:
                yield from prevs
                break
            first = False

            prevs.append(curr)
            print(prevs)

    return gen()

commenting out the if-statement

works for both test cases

deep_copy(safe_apply(rhs, curr, ctx=ctx))

yeah, but it seems that removing if curr == lhs and not first fixes the issue.

@lyxal I ported the code to a new file.

def index_indices_or_cycle(lhs, rhs):
    prevs = []

    def gen():
        curr = lhs
        first = True
        while True:
            curr = rhs(curr)
            print(curr)
            # if curr == lhs and not first:
            #     break
            if curr in prevs:
                yield from prevs
                break
            first = False

            prevs.append(curr)
            print(prevs)

    return gen()


# f = lambda n: (n + 1) % 3
f = lambda n: n + 1 if n < 3 else 3

no I mean that's how you apply function rhs

I know, I'm not in the poetry environment

wait I'll create a draft PR

the algorithm looks correct (and similar to what I had, but yours is shorter)

@mathcat oh, I believe I know why that was added

pretty sure that's not necessary, though.

It's for cases where applying the function returns the same value, hence not making it unique

But I suppose you're right that it's not necessary

eh, I changed my mind, I'll add it anyways

If you think so

I won't be around to merge for another 8 hours

Bed

o/

@lyxal hey, that does work without the if-statement.

cool.

mathcat4 opened pull request #1640 (Fix that keep-while-unique element bug) in Vyxal/Vyxal

oops I'm dumb, you don't need first at all

@user lmao I do not even remember writing that

alright I'll open an issue

hyper-neutrino opened issue #1641 (Evaluation on Existing Elements) in Vyxal/Vyxal

@lyxal No, the one I was asking for was Jelly's æc

@hyper-neutrino Thanks

@lyxal lgtm, I just wanna make some minor changes, which I'll do tonight

Feel free to yell at me if I forget :P

Oh

The bot ded

Aliven't

Operation no

Functionality isn't a thing for it

@emanresuA seems to be the same as Þk except it works on 1d arrays

Jelly

Vyxal

Huh

admittedly there seem to be a few bugs with shapes, but I think the general algorithm is the same

@Ginger where bepp bopp