Vyxal

For discussion about Vyxal. Repo: github.com/Vyxal/Vyxal | Org: ...
13:59
From the release notes, pertinent to earlier discussions :p
13:58
> For the foreseeable future, this will most likely be the very last non-bug fix update of all Vyxal versions. Personally, life is about to get busy for a while, and barring a flood of interest and other people able to contribute, I don't think I'd be able to make many changes at all. Nor do I feel like I would want to - as fun as getting 3.5 ready was, golflang development just doesn't have the same appeal it used to have. There's only so many SBCS shuffles one can deal with before the allure of not having a codepage to manage becomes ever so tempting :p. I think I'm ready to start moving
00:57
So tired of having to design within the constraints of a sbcs too :p
yst 23:57
ruler'd :p
yst 23:49
just as well
yst 23:49
you better not be deleting tests
yst 23:45
@Bridget no don't edit it I was planning on adding it back
yst 23:43
frickahh yaml cleaner
yst 23:43
interesting, no tests for × either
yst 23:42
@Bridget and tbh I didn't announce resignation, just most likely permanent stagnation
yst 23:41
enough people have code access that things could be self-managed if needed
yst 23:41
then I'd argue no heir needed
yst 23:40
would mean you'd need to give up your power over gambling and drinking though
yst 23:39
That'd be you if you'd want it :p
yst 23:39
like since about May last year
yst 23:38
I've been considering it for a while too
yst 23:37
(like the ones today :p)
yst 23:37
3.7.0 will most likely be the last release for a long time, barring crucial bug fixes
yst 23:37
But I think it's time for the mantle of big golf to be passed onto or taken up by someone else :p
yst 23:36
We had a good 5 year run, we came, we saw, and we (for some definition) conquered.
yst 23:36
@lyxal didn't mention it here, but I think I'll be winding things down in regards to Vyxal. Uni goes back tomorrow, and it'll be a busy year (final year stuff) meaning not much dev time available. Additionally, I think I'm ready to move on from golflang creation into praclang stuff
yst 23:34
@Bridget yeah given the whole winding stuff down thing :p
yst 23:34
was probably deleted in yaml sorting stuff :p
yst 23:32
would explain why the behaviour wasn't caught lol
yst 23:32
no tests for ÷
yst 23:32
there's uh
yst 23:32
huh
yst 23:30
i'll just use .vs for safety
yst 23:30
or I could just use .vs
yst 23:30
user, quick question, to the best of your knowledge, would an implicit conversion of String to VStr break everything?
yst 23:25
there is a slight chance I forgot to add it
yst 23:24
which would be good if I actually implemented things the right way around lol
yst 23:24
thus, regex split on ÷
yst 23:23
which, in reality, is never
yst 23:23
the only benefit of ÷ being normal would be if you wanted to vectorise normal splits
yst 23:22
Somehow, I managed to get them around the wrong way it seems
yst 23:21
so to make ÷ less useless, it should be a special case
yst 23:21
the theory being having both normal gives duplicate behaviour
yst 23:21
I don't know how this has happened, but the idea should be ÷ is regex, s is normal
 

 The Nineteenth Byte

The Nineteenth Byte: General discussion for codegolf.stackexc...
13:24
more like ganyYEET
 

 CG&CC-gaming

For CG&CC users to discuss and play video games and board game...
03:10
three full mix-and-match ready sets :p
03:08
yst 14:09
I was playing some sheep wars and got an invite out of the blue so I just accepted lol
yst 14:07
because somehow I managed to end up in a hypixel guild
yst 14:07
among grinding on hypixel for the guild fam
yst 14:07
anyhow, that's the stuff I've been doing since last photo update
yst 14:06
purely for fun lol
yst 14:06
 

The Honeypot :3

Unknown event dump for TNB.
yst 14:08
Nuh uh