« first day (594 days earlier)      last day (1181 days later) » 

05:13
DID ANYONE IMPLEMENT VARIABLES???
05:39
PyGamer0 approved on PR #310 (Vyxal/Vyxal): "You know; i didnt check this properly but ok."
ಠ_ಠ
 
1 hour later…
06:55
@emanresuA yes
it's just x that has issues
and X
probably because they're different tokens lol
there we go fixed
@emanresuA disabling branch protection is only for emergency patches/things that need to be instantly pushed
github.com/Vyxal/Vyxal/commit/… don't seem like it's an emergency
@AaroneousMiller github.com/Vyxal/Vyxal/commit/… don't seem like it either
like unless it's for something like AoC in 5 minutes or that the site is broken, branch protection should stay on
also @emanresuA you forgot to format your commit with black
07:26
^ pro advertising
08:01
@lyxal I used the web editor :P
@lyxal Nah, I just wanted it for a challenge.
And we forgot to reimplement it in the rewrite
Idea: What if we have vyxal-staging.pythonanywhere.com which pulls directly from main?
(Or sometihng like that)
@emanresuA well whatever you did the linter isn't passing anymore
Might need a trailing comma?
Yep, it was a single trailing comma.
Also
Note the scrollbar on the top right
I think there's more errors than we have code
08:18
@emanresuA those aren't errors those are warnings
Everyone knows you ignore warnings when programming :p
Still...
It's just because it's bad at recognising imports
It doesn't realise that those functions are actually defined
Oh :P
!!/run 5→x←x
[@emanresuA: 59765867]
⟨ 5 ⟩
⟨ 5 ⟩
Oh wait those are the buggy ones
08:26
Correct
!!/run 5→y←y
@lyxal 5
Ugh, why do we have to use package imports...
It's a huge pain if you're trying to work on it
import vyxal.encoding etc
So it can be pip installed and used as vyxal <args>
That doesn't work yet I don't think, but that's the plan
@emanresuA idk if it works without the package imports either
(cc anyone who's good at import management/package management) I don't even know if the file layout is optimal/well formatted
08:50
Also:
!!/run 12345f'
@emanresuA (output was empty)
The ' should just be a NOP, right?
chunkybanana opened PR #313 (Vyxal/Vyxal) (Vyxal:relative-imports → Vyxal:main): Adding relative imports
(It's a draft pr btw)
09:41
@emanresuA theoretically, yes.
Lyxal closed issue #305 (`°` doesn't do anything, Vyxal/Vyxal)
Lyxal closed issue #291 (No way to display a decimal, Vyxal/Vyxal)
Lyxal merged PR #310 (Vyxal/Vyxal) (Vyxal:decimals-and-complex-numbers → Vyxal:main): Decimals and complex numbers
@lyxal The actual error's something like('a function is not iterable'
10:27
!!/run 12345f' c
[@lyxal: 59766543]
STDERR:
stack.append(12345)

lhs = pop(stack, 1, ctx); stack.append(deep_flatten(lhs, ctx=ctx))

def _lambda_19edc310c1a3c82f96f9aa43be9c3fb4(arg_stack, self, arity=-1, ctx=None):
    if arity != -1: stack = wrapify(arg_stack, arity, ctx=ctx)
    elif 'stored_arity' in dir(self): stack = wrapify(arg_stack, self.stored_arity, ctx)
    else: stack = wrapify(arg_stack, 1, ctx)
    this = self
    ctx.function_stack.append(this)
    ctx.context_values.append(list(deep_copy(stack)) if len(stack) != 1 else deep_copy(stack[0]))
Seems like an issue with filter in general
 
2 hours later…
12:37
Lyxal opened PR #314 (Vyxal/Vyxal) (Vyxal:fix-312-and-list-printing → Vyxal:main): fix #312 and add spaces to some list printing
13:04
Lyxal deleted branch Vyxal/decimals-and-complex-numbers
!!/issue Vylight ° no longer does function reference it does complex numbers syntax-change outdated-highlighting
Vyxal-Bot opened issue #5 in Vyxal/Vylight: ° no longer does function reference
thank you vyxal bot
very good
@VyxalBot hug
@AaroneousMiller (づ。◕‿‿◕。)づ
13:12
good bot
Man the 05AB1E and Jelly repos look tame in comparison to ours
eg they only have 7 basic labels for issues and prs
we have 21.
they only have a few amount of repo tags
we have the maximum possible lol
but we're gluten free
they aren't
which is ultimately why Vyxal is superior
13:16
bruh how does jelly only have 319 commits?
also I fixed #312 and made a PR for it
@AaroneousMiller idk
@lyxal nice
@AaroneousMiller we have more commits than jelly and 05ab1e combined
2 mins ago, by lyxal
which is ultimately why Vyxal is superior
exactly
they haven't even reached 1k commits
while we're just chilling with almost 1.6k
13:19
And between all the golfing langs out there, we are the only one with a version guaranteed to have no bugs
precisely
hey who wants to see what v0.0.0 looked like?
Lyxal reopened issue #28 (Vectorised print commands not disabling implicit output, Vyxal/Vyxal)
that's for later this morning
!!/'night
@lyxal o/
👍
 
3 hours later…
16:46
AMiller42 approved on PR #314 (Vyxal/Vyxal): "looks good to me, also I really need that `I`"
AMiller42 merged PR #314 (Vyxal/Vyxal) (Vyxal:fix-312-and-list-printing → Vyxal:main): fix #312 and add spaces to some list printing
AMiller42 closed issue #312 (`I` doesn't work properly on lists, Vyxal/Vyxal)
AMiller42 deleted branch Vyxal/fix-312-and-list-printing
AMiller42 opened PR #315 (Vyxal/Vyxal) (Vyxal:main → Vyxal:production): Update Production (12/2/21)
@hyper-neutrino if you're not busy, you wanna approve that PR?
You could ask everyone for reviews through Gh itself
pxeger closed PR #313 (Vyxal/Vyxal) (Vyxal:relative-imports → Vyxal:main): Adding relative imports
@rues lol i forgot that there was actually a thing meant for that
17:01
AMiller42 merged PR #315 (Vyxal/Vyxal) (Vyxal:main → Vyxal:production): Update Production (12/2/21)
ooh pip insyall -e looks nice
the texan version of install
 
1 hour later…
18:13
AMiller42 opened issue #316 in Vyxal/Vyxal: Error with basic math operators
AMiller42 opened issue #317 in Vyxal/Vyxal: `Ḃ` does not work on integers ending in 0
AMiller42 opened issue #318 in Vyxal/Vyxal: Numbers starting with 0 error
18:29
leading 0s should just push more 0s
like 0042069 should just push 0 0 42069
or is that intended rn anyway
I'm pretty sure that's what was intended, but there was a typo or something in the implementation of it that is making it error
The relevant part of the traceback is Integer (00 )Integer (42069 ), where the second I is being marked as a syntax error.
18:44
# that is, if someone has been a sussy baka
# with their syntax (probably intentional).
Why do I feel like that comment was directed at me?
19:10
I gotta go for a little while, once I get back I'm going to mark my cop as safe and reveal the solution, so if anybody wants to crack it, this is your last chance: codegolf.stackexchange.com/a/237451/101522
I gotta go to so oh well
@VyxalBot Should be intterpreted as octal
Why not
o/
 
2 hours later…
21:08
Raise your hand if you guessed that the solution to my cop was just abusing some [Classic Vyxal Jankness]
21:30
@AaroneousMiller it actually isn't
It's a generic catch all people who are either noobs or doing something clever for restricted source
oic
Flashbacks to Print x without x
@AaroneousMiller a bunch of changes were done in largeish batches and there wasn't much work done by people other than dennis
ah
I'm gonna delete the function-names and more-generators branches in the repo, any objections?
I guess that's a no
AMiller42 deleted branch Vyxal/function-names
AMiller42 deleted branch Vyxal/more-generators
Hello Bereuzin, what brings you here?
21:49
Hey where did that vectorisation/generator tag go?
thats a good question
dw, i "found" it
AMiller42 created branch Vyxal/again
AMiller42 opened PR #319 (Vyxal/Vyxal) (Vyxal:again → Vyxal:main): (again)
Lyxal approved on PR #319 (Vyxal/Vyxal): "🗣️🦌🧊"
@VyxalBot proceed
hey lyxal, remember that code guide that took 20 revisions to get right? it's outdated, you should make it 21
22:05
W... Wdym?
22:30
Makonede opened PR #18 (Vyxal/SandboxMakonede/Sandbox) (Makonede:master → Vyxal:master): haha sussy baka lolol funy
23:09
Lyxal merged PR #18 (Vyxal/SandboxMakonede/Sandbox) (Makonede:master → Vyxal:master): haha sussy baka lolol funy
hey wait #18?
> 10 closed issues
I'mma be honest I didn't actually check what the contents of that PR were
23:35
Lyxal opened PR #320 (Vyxal/Vyxal) (Vyxal:fix-aaron's-bugs → Vyxal:main): fix #316 #317 #318

« first day (594 days earlier)      last day (1181 days later) »