« first day (682 days earlier)      last day (1093 days later) » 

02:15
Can you escape in backticks?
02:27
I don't know if that'll be needed yet
 
1 hour later…
03:33
chunkybanana opened issue #748 in Vyxal/Vyxal: `*` doesn't vectorise on functions.
 
5 hours later…
08:20
@VyxalBot Useless feature request go brr
 
3 hours later…
11:26
@VyxalBot what would that actually do?
how do vectorising functions work?
it's not vectorising functions
it's vectorising * when there's a function involved
because func * number changes the arity of that function to the number
Lyxal opened PR #751 (Vyxal/Vyxal) (Vyxal:add-a-call-to-ctx-in-vy-map-or-pair → Vyxal:main): Make things like input work again inside maps
oh, ok
11:28
it's undocumented right now
but I'm fixing that now
Lyxal opened PR #752 (Vyxal/Vyxal) (Vyxal:add-function-multiplication-documentation → Vyxal:main): Add documentation for the probably unknown feature of function multiplication
woah lyxal
super speed
11:54
@VyxalBot do we need tests for arity change/dyadify/triadify?
@mathcat I added those
it's all covered by mutliplication testing
d and T just call multiply for functions
that's the file, right?
the tests are in test_complex.py
oh
I thought those were for complex numbers
no, it's for tests that don't fit the "input, easily observable output" format
12:00
ah, ok
btw how are the tests generated from .yaml?
nice
and github actions runs the file?
correct
noice
I have to do some cool workflow things too.
12:16
@mathcat actually wait no
I just remembered it isn't the workflow that runs processor.py
the workflow runs the test cases
wait how?
that runs processor.py and pushes any changes if necessary
nice
don't ask me how it works though - pxeger set it up iirc
but it looks like you need to install the github application from the site I linked
and then you need a .pre-commit-config.yaml file
and it also only runs on PRs
as in, whenever you open a PR or push changes to a PR, it runs
12:23
all this time and I've never actually looked at how it works until now
@mathcat but that's fine, because the testing workflows only run on PRs too
We should totally document this somewhere

how does the pre-commit CI thing work?

4 mins ago, 2 minutes total – 5 messages, 1 user, 0 stars

Bookmarked just now by lyxal

I bookmarked my explanation
@user there's probably quite a few systems-related things we should document lol
Actually, I think I
why do I always hit enter
when pressing '
@lyxal like how to recreate vyxal bot if for some reason we ever need to, how to re-establish the online interpreter if someone ever uses an ACE exploit to rm -rf everything, what all the different webhooks do, organisation management guidelines, etc
@lyxal I hope nobody rm -rf's everything
12:29
everyone does
but who's sus
!!/sus
@mathcat ඞ
no wait
What was the command again?
!!/sus
@mathcat ඞ
!!/blame
12:30
@lyxal It was user's fault!
yikes
user you sus
I mean, user does have the power to delete everything
plus they don't have 2FA enabled (what a nerd)
meaning that if their password was ever leaked
well,
that'd be a frick situation
but that's an extreme hypothetical
and extreme hypotheticals are just that
hypotheticals that have a practically 0 chance of happening
and user is a koala
12:33
also, a surprising amount of people don't have 2FA enabled
@lyxal yeah, me, because I don't care
@mathcat I know you don't
the "people" list in the organisation shows who has 2FA enabled and who doesn't
I can't see it
12:36
ah
must be an admin thing
some old image I found
see first bullet point
uh
hmm
ngl that shouldn't be reported
@hyper-neutrino bot reports private repo issues
@VyxalBot make me a cookie
@lyxal No.
Rude.
12:47
@VyxalBot mak me cookie
@mathcat Here you go: 🍪
thanks!
Woooow. @VyxalBot can't believe you've done me like this
@VyxalBot make me a cookie
@lyxal Here you go: 🍪
Finally
Now I can go flex on olimar
12:48
wohoo
I'm off to eat cookies
13:22
@mathcat oh shit i must leave the vyxal group
ok im out
/s
Jul 6, 2021 at 12:26, by lyxal
I doubt I actually can
 
4 hours later…
17:12
@lyxal agree. nice plan
17:31
@lyxal mind if I steal your LazyList impl for myself?
 
5 hours later…
22:49
@Seggan I mean, yes you can, but I wouldn't recommend it.
Bad code? ;)
It's had a very buggy history
You should check out pxeger's libgolf
It's better and less vyxal specific
my current impl does fine, except in a single challenge where normal vyxal seems to somehow lazily filter a huge range. Jyxal would have to compute the range first
23:05
@Seggan that's the beauty of lazy evaluation. You can do stuff on big ranges and it doesn't actually calculate anything until output is needed
@Seggan Would you like help implementing the lazylists?
@lyxal Could you implement the changes here or should I or should we just leave them?
@user I'm not at my computer currently, but I think it's fine
Aww, I was hoping you'd say you'd implement them because I'm too lazy to :P
Lyxal closed issue #748 (`*` doesn't vectorise on functions., Vyxal/Vyxal)
Lyxal merged PR #749 (Vyxal/Vyxal) (Vyxal:make-multiply-vectorise-with-functions → Vyxal:main): As requested, `*` now vectorises if there's a function
Lyxal deleted branch Vyxal/make-multiply-vectorise-with-functions
@user Doesn't matter - it's fine the way it is
23:21
@user you any good at java?
Eh, I'm more of a Scala guy but I've got a decent amount of experience with Java
feel free to pr
Aight
my current impl is in runtime/lists
23:38
@Seggan You seem to be mapping and filtering lists in place, which could be a problem, since the Python implementation of Vyxal creates new lists
I'm going to just rename that to mapInPlace and filterInPlace and create new map and filter methods returning new lists real quick

« first day (682 days earlier)      last day (1093 days later) »