« first day (656 days earlier)      last day (1117 days later) » 

05:47
@emanresuA all the alternate algorithms I'm finding for combinations without replacement all require len
and that's what we're trying to avoid
Ok I guess...
we can focus on hyperspeed efficiency when we migrate to scala
wait are we actually planning on vyxal 3
Yes
It's a serious thing
Have you not seen the roadmap that details v3 progress?
06:09
no i haven't been paying attention here for too long
Nov 17 '21 at 5:03, by hyper-neutrino
ngl better roadmap than SE
I figured you had known. Doesn't matter lol
In any case, yes version 3 is a real thing
It's not just some in-joke
Has anyone tried running Vyxal in rust-python?
 
5 hours later…
11:16
Lyxal opened PR #705 (Vyxal/Vyxal) (Vyxal:assorted-digraphs → Vyxal:main): Add: shortest of a list (`Þg`), longest of a list (`ÞG`) and sort by length (`Þṡ`)
hey guys make sure you update your version of black to version 22.1.0
that's if you use autoformatting
because there's been a few changes to the autoformatting rules
like now it removes spaces between **
11:40
[deepsource-autofix[bot]](github.com/deepsource-autofix[bot]) created branch Vyxal/deepsource-fix-ef91b164
[deepsource-autofix[bot]](github.com/deepsource-autofix[bot]) opened PR #706 (Vyxal/Vyxal) (Vyxal:deepsource-fix-ef91b164 → Vyxal:main): Refactor unnecessary `else` / `elif` when `if` block has a `break` statement
11:55
@lyxal Interesting
I know this from the commit the ci thing made
I was like "what? why'd you need to reformat with black? vs code already auto-formatted"
and then I remember that it updated itself not that long ago
 
2 hours later…
14:19
!!/ run `2**2
@mathcat 2**2
!!/run `2 ** 2
@mathcat 2 ** 2
!!/run 2 4**
@PyGamer0 0
14:23
hm lol
no
just wanted to test
how it looks
i am doing my own thing
!!/run 2 0.5e
@PyGamer0 14142135623730950488016887242096980785696718753769/10000000000000000000000000000000000000000000000000
 
1 hour later…
15:44
Does Vyxal have a shuffle function?
nvm
 
2 hours later…
18:14
@mathcat Yep, Þ℅
18:42
Is there a type check in Vyxal?
Nothing explicit, but there are a couple of tricks you can use
What do you want to typecheck between?
actually, I just wondered if there was one
But how can I typecheck list vs. int?
18:58
So Vyxal uses base 161-encoding for the dictionary.
Is it certain that a compressed word will consist of 2 characters?
@mathcat :- will give truthy for list and falsy for int/string
nice hack
Wait lemme make a list
I'll try the rest myself
I'll let you know ~~when I have everything~~ when I give up
Sometimes SE chat is gonna give you up
@mathcat yep, each SCC (short character code) is two bytes.
19:14
Gah, I'm getting a serve rerror
19:32
Why is boolfiy vectorising?
⟨1|2|3⟩ should be 1
not ⟨0|0|0⟩
!!/run ⟨1|2|3⟩ḃ
@emanresuA ⟨ 1 | 1 | 1 ⟩
That is a bug.
nice
lemme make issue
Tams-Tams opened issue #708 in Vyxal/Vyxal: Boolify `ḃ` is vectorising
19:43
lemme try to fix it
Wait, it's a feature, not a bug
You have to explicitly use the t flag to get the Python behavior
@lyxal Can we not vectorise by default? It'd make more sense to do it the Python way
yes
anywhat I'll implement it for practice
19:57
Wow contributing is really easy
just update, test and commit
I was expecting:
@mathcat That's good to hear!
Are there any advantages of branches than forks?
!!/night
ah well
 
3 hours later…
23:09
So there's been an issue to vectorise and an issue to not vectorise
Which is it?
@AaroneousMiller *string compression code
23:52
(also thanks for approving my PR lyxal)
cgccuser merged PR #711 (Vyxal/Vyxal) (Vyxal:main → Vyxal:production): Update production (3/2/22)

« first day (656 days earlier)      last day (1117 days later) »