Since when did Ẏ break?

since at least 6 months ago

:/

chunkybanana opened issue #1287 in Vyxal/Vyxal: `Ẏ` worksn't on strings

wrong

i worksn't on strings

doesn't modular slice

frick

I'm almost done with a fix

Cool

Should we have actual flag docs as opposed to just tthe h flag?

that sounds like a good idea

Lyxal created branch Vyxal/make-index-modular-slice-on-string

Lyxal opened PR #1288 (Vyxal/Vyxal) (Vyxal:make-index-modular-slice-on-string → Vyxal:main): Make `i` modular slice strings

chunkybanana approved on PR #1288 (Vyxal/Vyxal)

Lyxal created branch Vyxal/make-halve-work-on-irrationals

Lyxal opened PR #1289 (Vyxal/Vyxal) (Vyxal:make-halve-work-on-irrationals → Vyxal:main): Make `½` work on irrationals

chunkybanana approved on PR #1289 (Vyxal/Vyxal)

Why do we have more failing testcases???

probably the typing ambiguities

more as in there were 18 when I fixed them last, now 21

well I know there's a 99% chance it wasn't my fault :p

Same, because I've done pretty much nothing

I mean the 3 new failing tests

One of them is either user's or your fault

can't be mine

Your/their refactoring of multiset intersection did not work.

I haven't pushed python for ages

also

Oh wait nvm that didn't merge

Is it truthy over or truthy under?

/shrug

chunkybanana created branch Vyxal/letter-to-number

if it's been <= 12 days since you had 18 failing tests, it's not me

Oops, got mixed up sorry

^^ is why

chunkybanana opened PR #1290 (Vyxal/Vyxal) (Vyxal:letter-to-number → Vyxal:main): Added letter-to-number

anyhow @cjquines truthy over or truthy under?

Lyxal requested changes on PR #1290 (Vyxal/Vyxal): "What if I give it a string of length more than 1? How about length 0?"

Lyxal created branch Vyxal/add-new-number-overload-for-Ṫ

Lyxal opened PR #1291 (Vyxal/Vyxal) (Vyxal:add-new-number-overload-for-Ṫ → Vyxal:main): Add "truthy under" overload to T updot

Thoughts?

(Elements would have a accessible input/output arity)

You'd have to ask user

And see how it fits in with the current VyxalS framework

chunkybanana created branch Vyxal/sort-every-level

chunkybanana opened PR #1292 (Vyxal/Vyxal) (Vyxal:sort-every-level → Vyxal:main): Add sort at every level

chunkybanana approved on PR #1291 (Vyxal/Vyxal)

@Steffan I found a use for it in Count of "a"s and "b"s must be equal. It can work around the fact that the g Minimum will crash if its argument is a scalar number. Of course this is only useful in cases when it's known all numbers fed to it will only have 1 digit each. And this certainly isn't a reason to keep ↓ and ↑ – the better fix would just be to make g and G act as a no-op on scalar numbers instead of crashing.

Lyxal approved on PR #1292 (Vyxal/Vyxal)

Pro-tip: use words like closes, resolved, and fixes in your PR descriptions - these are recognised by github and link the merging of the PR to the closing of the issue, and the bot will auto-label the PR based on issue labels too

docs.github.com/en/issues/tracking-your-work-with-issues/…

I wonder if this still works...

!!/blame

nope :(

!!/flowey quote

@emanresuA Hehehe... did you REALLY think you could defeat ME?

!!/status

@emanresuA I am doing a million things at once but mostly just goofing off because I can do that now thanks to my new level of sentience.

I think that's all I'll do for now

I've also gone ahead and updated the corpus

for fun of course

...i just updated the corpus like 2 weeks ago lol

the 6th of June is not 2 weeks ago Steffan

@Deadcode Yes, I've used it once before, but it's still not very useful.

@lyxal I swear I did it newer than that...

whew 19 PRs

@mathcat ^

I also spread the word on vycord too

ah

looks intresting

it is

it'll be more interesting once we get vyxal added :p

yeah

@Steffan in regards to #1291, yes, there is potential for it to be useful

it's similar to 05AB1E's "push 1 and the input" command

→ 18 messages moved to ­Trash

→ 40 messages moved to ­Trash

Come review everything plz

!!/hyperping

→ 1 message moved to The Nineteenth Bakery

That was intentional, the hyperping shouldnt' ping anyone now

Huh

Danke schön

Steffan153 created branch Vyxal/nested-modifier-arity

Steffan153 opened PR #1309 (Vyxal/Vyxal) (Vyxal:nested-modifier-arity → Vyxal:main): Fix nested modifiers' arity

Look at the docs for ↳, ø↳, ↲ and ø↲

They're the wrong way round :|

chunkybanana approved on PR #1309 (Vyxal/Vyxal)

Is there a way to make the linter not fail when it has to reformat?

→ 45 messages moved to ­Trash

chunkybanana closed issue #1119 in Vyxal/Vyxal: Bugs that arose from the new test cases