« first day (620 days earlier)      last day (1155 days later) » 

00:10
Lyxal created branch Vyxal/fix-515
Lyxal opened PR #519 (Vyxal/Vyxal) (Vyxal:fix-515 → Vyxal:main): Fix #515
chunkybanana approved on PR #519 (Vyxal/Vyxal): "This *will* invalidate all Vyxal 2.6 answers with compressed strings - right thing to do tho"
pxeger requested changes on PR #519 (Vyxal/Vyxal): "Can you add tests for this?"
chunkybanana opened PR #520 (Vyxal/Vyxal) (Vyxal:roman-numerals → Vyxal:main): Roman Numerals
how are there merge conflicts?
Oh I see
I checkout'd from the wrong branch
lol
I resolved them for you
because the github web extension I use allows for quicker conflict resolution
Thanks lol
git is pain sometimes
Copilot wrote like 90% of it
00:23
I was going to say, some of the stuff looks very reminiscent of copilot
It's a shame copilot doesn't really do Scala
yeah, it's sad.
00:56
I for one am very happy about that ;)
Y'all youngins were gettin' lazy with that newfangled AI cr*p
we still have to proofread it though
When I was your age, all we had was IntelliSense and TabNine
copilot just speeds things up
if it wasn't for copilot, the rewrite would have taken longer
You don't need Copilot to speed things up, just your God-given fingers and Intellisense
@lyxal We could probably copy over our existing Python code to some amount
You should try out TabNine though, it's not as smart as Copilot but it does help me with shorter snippets
Apparently it kinda works?
I think it can adapt to whatever language is being used
like for example it's able to autocomplete the YAML
even though I don't think YAML would have been that prevalent in the training data
01:02
Ah, I guess there's a lot of YAML and Scala on the internet
@lyxal It's used pretty commonly, not as much as JSON, but still
@user it's not laziness, it's called working smarter not harder ;p
ಠ_ಠ Stop being smart with me! Kids these days need to work harder!
Now git off my lawn!
ok code boomer
01:17
See what happens when you use Copilot?! :P
That's a pebkac error
anyhow I need the corpus code and I can't find it
@emanresuA do you have the corpus code?
oh nvm
just realised I left it on the issue
lol
01:31
chunkybanana closed issue #444 (Roman numeral builtins, Vyxal/Vyxal)
chunkybanana merged PR #520 (Vyxal/Vyxal) (Vyxal:roman-numerals → Vyxal:main): Roman Numerals
chunkybanana deleted branch Vyxal/roman-numerals
Lyxal closed issue #515 (Base-255 compression trims leading `a`s, Vyxal/Vyxal)
Lyxal merged PR #519 (Vyxal/Vyxal) (Vyxal:fix-515 → Vyxal:main): Fix #515
Lyxal deleted branch Vyxal/fix-515
CMP: Everyone okay with chunky's suggestion of making % do formatting for strings and numbers? I think it's more useful than the current behavior
@lyxal can you teach me a (bit) of vyxal
@user yes, I think it's fine
@Fmbalbuena what would you like to learn?
NOP in vyxal?
Space, newline
01:45
i suggest changing # to two spaces
02:11
@user My name's chunky now lol
Fmbalbuena opened issue #521 in Vyxal/Vyxal: Change "#" to two spaces
chunkybanana closed issue #521 (Change "#" to two spaces, Vyxal/Vyxal)
Who is Chunkybanana?
Me
Also:
- Significant whitespace in that way messes up indenting for readability
- Vyxal's made to feel like a traditional language, and comments are an important part of that
- Useful for polyglotting with Python
ok
more notes?
@emanresuA who is ysthakur?
user's old account
02:23
@emanresuA can i post discussion?
About what?
 
3 hours later…
05:29
chunkybanana opened PR #522 (Vyxal/Vyxal) (Vyxal:lgtm-fix → Vyxal:main): Fix everything lgtm was complaining about
Lyxal requested changes on PR #522 (Vyxal/Vyxal): "The test cases need that math import. "
 
4 hours later…
09:47
pxeger reopened issue #521 (Change "#" to two spaces, Vyxal/Vyxal)
10:00
pxeger created branch Vyxal/pypi
pxeger opened PR #523 (Vyxal/Vyxal) (Vyxal:pypi → Vyxal:main): Add GitHub actions workflow to build and publish package to PyPI
10:21
Lyxal approved on PR #523 (Vyxal/Vyxal): "The proposed package ownership plan seems reasonable. Perhaps the test release tag could be 2.7.2.1"
@pxeger idk why I didn't do this sooner, but I've added you to the organisation owner list
3
Welcome aboard :p
It's only fitting seeing as how you manage the majority of administrative matters
10:43
does vyxal have triadic elements?
10:57
Could someone explain this # thingy to me?
@PyGamer0 yes, it does
@mathcat so # is the comment character
like it is in python and other langs that use # for comments
however, vyxal is also a golfing language
comments aren't usually a feature of golfing languages
because, y'know, comments don't actually do anything
so why have comments? because it's just another nice practical feature from normal languages
now what #521 was originally suggesting was that comments be 2 spaces instead of #
1 1+  this is the comment
yeah I know, and we're keeping the comment feature
11:01
oh
I see
we're just thinking of which character to make it
and pxeger suggested to use a character not in the codepage
that way, comments are still a thing, but it isn't taking up a command that could be used for golfing
ok, thx
nice idea
I thought so too
now we just have to choose a character
amogus
whats with this random symbol?
looks a bit like hash/star
@lyxal cough cough flax
@lyxal lamp symbol
apl
i am using it
@lyxal let me yoink that idea
11:29
@lyxal you'd have to copy-paste that every time though
@mathcat that is true, but if you're using the vy.pa interpreter it's just point and click
oh right
 
1 hour later…
12:33
Lyxal opened PR #524 (Vyxal/Vyxal) (Vyxal:fix-date-constants → Vyxal:main): use datetime.now() instead of storing it at the beginning
Lyxal opened PR #525 (Vyxal/Vyxal) (Vyxal:update-poetry-lock → Vyxal:main): Update poetry.lock
Lyxal merged PR #525 (Vyxal/Vyxal) (Vyxal:update-poetry-lock → Vyxal:main): Update poetry.lock
Lyxal deleted branch Vyxal/update-poetry-lock
12:59
!!/'night
@lyxal o/
 
3 hours later…
15:39
@VyxalBot This is exciting
Idea: we move # out of the codepage and replace it with another character. That way, comments still use #, they just force utf8
16:15
@user uh
Is there a builtin to calculate n**n?
duplicate then power
??
!!/run ?:e _ 2
@grandBagel 4
how can I map that over a list?
16:24
@grandBagel i guess make a function / lambda then vectorise?
how to use ƛ?
ok i will go read docs cause even idk vyxal lol
!!/run ƛ:e ` ` [1,2]
@PyGamer0 ⟨ ⟩
16:32
!!/run ⟨ 1 | 2 | 3 | 4 ⟩ ƛ:e
@user ⟨ 1 | 4 | 27 | 256 ⟩
@user does it take the next 2 elements?
or until ;
Until ; (or the end of the program)
and the lambda is directly applied?
16:34
Well, ƛ isn't just a lambda, it also maps the lambda over the elements of the list
tbh I think vectorization is enough, you don't even need to map it
!!/run ⟨ 1 | 2 | 3 | 4 ⟩ :e
@user ⟨ 1 | 4 | 27 | 256 ⟩
!!/run ⟨ 1 | 2 | 3 | 4 ⟩ e
@user ⟨ 0 | 0 | 0 | 0 ⟩
Okay that doesn't work
is the bot <input...> <code>?
!!/run ⟨ ⟨ 1 | 2 | 3 | 4 ⟩ | ⟨ 5 | 6 | 7 | 8 ⟩ ⟩ :e
@PyGamer0 ⟨ ⟨ 1 | 2 | 3 | 4 ⟩ | ⟨ 5 | 6 | 7 | 8 ⟩ ⟩
wut
Why didn't it work?
!!/run ⟨ ⟨ 1 | 2 | 3 | 4 ⟩ | ⟨ 5 | 6 | 7 | 8 ⟩ ⟩ ⟨ ⟨ 1 | 2 | 3 | 4 ⟩ | ⟨ 5 | 6 | 7 | 8 ⟩ ⟩ e
@user ⟨ ⟨ 1 | 4 | 27 | 256 ⟩ | ⟨ 3125 | 46656 | 823543 | 16777216 ⟩ ⟩
!!/run ⟨ ⟨ 1 | 2 | 3 | 4 ⟩ | ⟨ 5 | 6 | 7 | 8 ⟩ ⟩ ƛ:e
16:37
@PyGamer0 ⟨ ⟨ 1 | 2 | 3 | 4 ⟩ | ⟨ 5 | 6 | 7 | 8 ⟩ ⟩
wat lol
Okay yeah I'm not sure why it isn't working for you
Oh you're putting them in two separate code thingies
Put them in a single `thing`
!!/run ⟨ ⟨ 1 | 2 | 3 | 4 ⟩ | ⟨ 5 | 6 | 7 | 8 ⟩ ⟩ ƛ:e
16:38
@PyGamer0 ⟨ ⟨ 1 | 4 | 27 | 256 ⟩ | ⟨ 3125 | 46656 | 823543 | 16777216 ⟩ ⟩
@PyGamer0 That's just how Jelly works when you treat a dyadic thing as monadic
@user it does the job
!!/run Πƛ:e _ 8
@grandBagel ⟨ 1 | 4 | 27 | 256 | 3125 | 46656 | 823543 | 16777216 ⟩
@user flax also does the same
16:39
It would be more helpful to duplicate the input than pop 0 from an empty stack, honestly
@VyxalBot why no product?
!!/run 8ʀƛ:e;Π
@PyGamer0 55696437941726556979200000
@grandBagel ^?
yes
how does it work?
!!/run 8ʀƛ:e;Π _ 6
16:47
@grandBagel 55696437941726556979200000
why the same?
17:02
!!/run ?ɾ‡:eΠ _ 8
[@grandBagel: 59999729]
STDERR:
Traceback (most recent call last):
  File "/home/Vyxal/mysite/vyxal/main.py", line 147, in execute_vyxal
    exec(code, locals() | globals())
  File "<string>", line 27, in <module>
  File "/home/Vyxal/mysite/vyxal/elements.py", line 2769, in product
    return vy_reduce(multiply, lhs, ctx=ctx)
  File "/home/Vyxal/mysite/vyxal/elements.py", line 4039, in vy_reduce
    return {
  File "/home/Vyxal/mysite/vyxal/elements.py", line 4043, in <lambda>
    (types.FunctionType, ts[1]): lambda: foldl(
cgccuser created branch Vyxal/lgtm-fix-1
cgccuser opened PR #526 (Vyxal/Vyxal) (Vyxal:lgtm-fix-1 → Vyxal:main): Heed an LGTM alert
17:22
cgccuser opened PR #527 (Vyxal/Vyxal) (Vyxal:lgtm-badges → Vyxal:main): Add LGTM badges to README
cgccuser opened PR #528 (Vyxal/Vyxal) (Vyxal:workflow-names → Vyxal:main): Make deploy yml file name match workflow name
cgccuser closed PR #528 (Vyxal/Vyxal) (Vyxal:workflow-names → Vyxal:main): Make deploy yml file name match workflow name
@grandBagel Not necessarily, although we do need better error messages
Oh wait, I think it is a bug, the arguments need to go in the opposite order
My bad lol
I'll fix it later, too tired rn
18:10
@grandBagel You're taking the product of a function lol
@user should it be an issue?
better error messages?
Probably, yeah
@VyxalBot Context of this: product runs reduce by multiply, reduce runs foldl, which does a length check, but functions are lengthless.
!!/ issue Better error messages basically Vyxals using pythons default error messaging and it'll help a lot if we change those to be more understandable
@mathcat !!/issue repository **title** body `label` `label` - if the repository is not specified, it assumes Vyxal/Vyxal; the body can be omitted but it is recommended that you write a description; at least one label is required
18:21
ey
oh
!!/ issue **Better error messages** basically Vyxals using pythons default error messaging and it'll help a lot if we change those to be more understandable
`enhancement`
(message response failed or the new message is not a command)
ugh
!!/ issue **Better error messages** basically Vyxals using pythons default error messaging and it'll help a lot if we change those to be more understandable
`enhancement`
!!/issue Better error messages basically Vyxals using pythons default error messaging and it'll help a lot if we change those to be more understandable enhancement
Vyxal-Bot opened issue #529 in Vyxal/Vyxal: Better error messages
YES
sobbing I've always wanted to use that command
18:38
damn imagine finding good reasons to use commands
chunkybanana opened issue #530 in Vyxal/Vyxal: `c` doesn't work on strings
most ppl here just spam commands for no reason (even if they don't need anymore testing) just for fun :Exit:
chunkybanana merged PR #523 (Vyxal/Vyxal) (Vyxal:pypi → Vyxal:main): Add GitHub actions workflow to build and publish package to PyPI
chunkybanana deleted branch Vyxal/pypi
chunkybanana approved on PR #524 (Vyxal/Vyxal): "This *might* have been my fault... ;)"
Lyxal merged PR #524 (Vyxal/Vyxal) (Vyxal:fix-date-constants → Vyxal:main): use datetime.now() instead of storing it at the beginning
Lyxal deleted branch Vyxal/fix-date-constants
Ok wow Lyxal is speed even at 5am
wooa
19:24
@emanresuA how can I make it take the product of the list?
What list?
the list that contains the exponents
Oh... get rid of the
grabs the next two elements into a function
I thought it defined a two-byte lambda...
Same thing, pretty much
Anyway, that's the thing pushed to the stack before runniing product
19:55
@lyxal muahahahaha, this was my plan all along! Now I shall use my powers to turn everyone else who works on Vyxal into frogs!
pxeger deleted a discussion in Vyxal/Vyxal: Haha funny number
get 13'd
cant be frog, am plat
this is a threat
20:30
pxeger commented on PR #527 (Vyxal/Vyxal): "I'm not really a fan of excessive badges in the README, so I won't approve"
pxeger deleted branch Vyxal/workflow-names
pxeger opened PR #531 (Vyxal/Vyxal) (Vyxal:make-test-release → Vyxal:main): Make test relesae v2.7.2.post1
 
2 hours later…
22:48
@emanresuA the joys of auto-merge.
I can claim merges even when I'm asleep
23:31
cgccuser opened PR #532 (Vyxal/Vyxal) (Vyxal:518 → Vyxal:main): Implement 518
cgccuser opened PR #533 (Vyxal/Vyxal) (Vyxal:gen-tests → Vyxal:main): Generate tests in the test workflow
cgccuser opened PR #534 (Vyxal/Vyxal) (Vyxal:fewer-badges → Vyxal:main): Remove a few badges
We have a ridiculous number of PRs and issues now (both total and current)
23:50
@pxeger but I am already plat tho
@pxeger Why frogs specifically?
pxeger approved on PR #534 (Vyxal/Vyxal): "This is much more sensible tbh"
@user idk that's just what witches do
@grandBagel just a little tip: Since implicit input also exists in lambdas, you can typically remove the starting : in a lambda
23:53
Can't you turn us into unicorns or something?
I want to go impale some people, so much cooler than puking up your stomach
Lyxal approved on PR #534 (Vyxal/Vyxal): "Remind me to add something from deepsource too"
cgccuser merged PR #534 (Vyxal/Vyxal) (Vyxal:fewer-badges → Vyxal:main): Remove a few badges
cgccuser deleted branch Vyxal/fewer-badges
pxeger closed issue #518 (`%` should do format on (string,number), Vyxal/Vyxal)
pxeger merged PR #532 (Vyxal/Vyxal) (Vyxal:518 → Vyxal:main): Implement 518
pxeger deleted branch Vyxal/518
pxeger requested changes on PR #533 (Vyxal/Vyxal): "This needs to install `yaml` first"
Yeah
Lyxal approved on PR #533 (Vyxal/Vyxal): "Maybe also add something later for documentation rerolling"

« first day (620 days earlier)      last day (1155 days later) »