« first day (1369 days earlier)      last day (406 days later) » 

00:13
F
got starbombed again
00:48
in The Nineteenth Byte, 27 secs ago, by lyxal
It was a massive wave in at least 6 different rooms
 
10 hours later…
10:41
RubenVerg pushed a commit to Vyxal/v3-vectorizing-not-equals in Vyxal/Vyxal: Make vectorize
RubenVerg created branch v3-vectorizing-not-equals in Vyxal/Vyxal
RubenVerg opened pull request #2068 (Make vectorize) in Vyxal/Vyxal
github-actions[bot] pushed a commit to Vyxal/v3-vectorizing-not-equals in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
 
1 hour later…
12:12
lyxal approved #2068 (Make vectorize) in Vyxal/Vyxal
lyxal merged pull request #2068 (Make vectorize) in Vyxal/Vyxal
lyxal deleted branch v3-vectorizing-not-equals in Vyxal/Vyxal
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Make vectorize
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Merge pull request #2068 from Vyxal/v3-vectorizing-not-equals
lyxal approved #2063 (Make trigraphs in digraphs work) in Vyxal/Vyxal
lyxal merged pull request #2063 (Make trigraphs in digraphs work) in Vyxal/Vyxal
lyxal deleted branch digraph-trigraphs in Vyxal/Vyxal
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Make trigraphs in digraphs work
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Add test
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Merge branch 'version-3' into digraph-trigraphs
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Merge pull request #2063 from Vyxal/digraph-trigraphs
mfw no bridget
 
1 hour later…
13:18
@Ginger bridget dead
me when
13:41
test
[Ginger] we are so back
Brogle back
 
2 hours later…
15:46
GingerIndustries pushed a commit to vyxal.github.io/theseus in Vyxal/vyxal.github.io: Load theseus.json from local files when in archive mode
GingerIndustries pushed a commit to vyxal.github.io/theseus in Vyxal/vyxal.github.io: Bind worker event handlers correctly to prevent multiple prints
GingerIndustries pushed a commit to vyxal.github.io/theseus in Vyxal/vyxal.github.io: Fix codepage table row elements lacking a key
@RubenVerg the repeated-print bug with theseus is now fixed
[RubenVerg] was literally about to write a message asking how hard the theseus code is to approach because I wanted to fix that bug
[RubenVerg] thanks (:
16:01
np :p
turned out to be the worker event handler being attached repeatedly
[RubenVerg] oh you also fixed the one where it loaded the theseus file from elsewhere instead of from vy-archive, thanks again
[RubenVerg] oh, theseus is react? ):
@Bridget yes
no way I was doing all the DOM-fiddling myself
@Bridget that works? cool
16:22
GingerIndustries pushed a commit to vyxal.github.io/theseus in Vyxal/vyxal.github.io: Fix copy button accessible title in share dialog
@lyxal what's the latest on highlighting for the new syntax?
GingerIndustries pushed a commit to vyxal.github.io/theseus in Vyxal/vyxal.github.io: Remove legacy source files from old site
mfw theseus has 2.5k sloc
[user] Yeah, check out Functions.scala. You can do Monad.vectorise, Dyad.vectorise, etc.
[user] No American spelling, I'm afraid \:(
[RubenVerg] oh you just made me realize the code spells vectorize with an S
17:02
[RubenVerg] I'm struggling to convert this line of Haskell code into Scala, could anybody help me? iota = foldr (liftA2 (:) . enumFromTo 1) [[]]
this function basically creates a flat list containing all multidimensional indices generated by the input list, APL style
[RubenVerg] playground
[RubenVerg] (apl-style ranges turn out to be kinda harder than I thought)
@Bridget [Vendethiel] Apply.map2 of (_ :: _)?
GingerIndustries pushed a commit to vyxal.github.io/theseus in Vyxal/vyxal.github.io: Remove debugging code in permalink.ts
GingerIndustries pushed a commit to vyxal.github.io/theseus in Vyxal/vyxal.github.io: Move data files from assets/ into a new data/ directory
GingerIndustries pushed a commit to vyxal.github.io/theseus in Vyxal/vyxal.github.io: Fix incorrect splash URL in latest.html
[RubenVerg] I'm dumb, I just had to implement manually the Applicative instance for lists
[RubenVerg] came up with seq.foldRight(Seq(Seq.empty[Int])) { (el, acc) => for { e <- (1 to el); a <- acc } yield e +: a }
[RubenVerg] oh wait I forgot there's no reshape function
17:29
[Ginger] I think theseus is almost ready for prime time
[Ginger] once lyxal fixes the highlighter, that is :knuth:
[Ginger] only took me... over a month longer than I expected lol
[RubenVerg] yeah no I don't think I can figure out reshape by myself
[RubenVerg] once somebody more clever than me implements reshape I'll open a pr for apl-style multidimensional ranges
[Vendethiel] not winning any conciseness award:
vec.foldRight(Vector(Seq.empty[Int])) { (el, acc) => ((1 to el).toVector, acc).mapN(_ +: _) }
@Bridget [Bridget ⚙] Edit ignored due to edit window expiring, sorry!
18:00
@Bridget [user] We do have cartesian product already, maybe you could use that? cartesianProductMulti(seq.map(1 to _))
[RubenVerg] yes, looks to be equivalent
[RubenVerg] the problem is in the reshaping to a nested list
[RubenVerg] unless we want the code to actually return a flat list, which is also an option
hi sorry for the noob question, what do you put in place of lambda args in λ lambda args | code }
18:19
[that mac] stuff like a b c ... iirc
!!/status
@Ginger I am playing an even more difficult and challenging game called "Lava doesn't exist, you idiot. Now give me your money."
[user] Okay this is much more complicated than I thought
[user] If we allow referring to elements defined later in a file, then what do we do about custom elements defined inside structures (like functions?)
[user] Ugh
[user] (and we have to allow referring to custom elements defined later in a file, in case the element is referred to inside a function and the function is only called when the custom element gets defined)
multiline
[user] One solution is to only allow defining custom elements at the toplevel
[user] Aaaa kinda wish we didn't have arity grouping
[user] It requires statically resolving elements, at parse time aaaa
[user] I'm gonna make another parsing phase
[user] No one can stop me
[that mac] history is being written
[user] git history
[that mac] a new parsing phase shall be created
@Bridget [that mac] ಠ_ಠ
[user] And on the 16th day, user said, let there be LiteParser
[user] You're killing me mathcat
[user] You can't start typing and stop over and over again
[that mac] right
18:39
he's trying to find the right words
[user] All that time to write right
maybe he types slow?
[user] I already know I'm right, I'm always right
no, you're user
@Ginger [user] No it was definitely intentional
[that mac] keep theorising yall
@Ginger [user] ._.
18:40
:3
[user] You dare use my Lyxal's tricks against me
yup
[user] I hate you all
[user] Send your messages THIS SECOND
[AlanTheBagel] no
[RubenVerg] oh I have no message I just wanted to annoy you (:
[user] asd;lfjaws;djfasd
@Bridget [that mac] well you know where this is going to end up
[user] I flood the codebase and start anew with some inbred animals?
[Ginger] this is fun
[that mac] hey this feels automatable
[AlanTheBagel] it should be
[Ginger] write a script that makes you constantly show as typing
[Ginger] ddos Rydwolf :disturb_smile:
[user] NO
[Ginger] shocking
@Bridget [AlanTheBagel] i think i did it
so it would seem
[AlanTheBagel] did it work?
18:45
quick, someone give me some Vyxal 3 code that looks fancy
for our website
[user] Fizzbuzz
@Bridget [user] Not really, you stopped for a moment there
@Bridget [AlanTheBagel] intentional
[user] I see
me omw to write the shittiest fizzbuzz program possible
well then
[AlanTheBagel] ah yes, 3.4.1 is incompatible with 3.4.1
@Ginger [AlanTheBagel] any vyxal code thats >= 5 chars
[user] So I'm thinking that we can allow referring to custom definitions made later, and it'll resolve definitions statically, then do the arity grouping afterwards
[user] Should be manageable, will just add another step to the parser
[user] Working on it rn, will push the branch when I have something commit-worthy
GingerIndustries pushed a commit to vyxal.github.io/theseus in Vyxal/vyxal.github.io: Unbork permalink compatibility checker
@Bridget [Bridget ⚙] Edit ignored due to edit window expiring, sorry!
19:04
behold, fizzbuzz: ɾƛ3Ḋ[kf|5Ḋ[kb|}
[AlanTheBagel] how does it work? (im not very good at vyxal)
it's pretty much a literal translation of the fizzbuzz algorithm to Vyxal
[AlanTheBagel] ok
[AlanTheBagel] wait what theres no fizz or buzz in the program how does it output fizz and buzz?
kf and kb are constants for "Fizz" and "Buzz" respectively
[AlanTheBagel] ah ok
19:07
ɾƛ3Ḋ[kf|5Ḋ[kb works too, apparently
[AlanTheBagel] im going to try fizzbuzz myself
@Ginger [user] Maybe try showing off string compression instead
[user] Also, is the } necessary?
3 mins ago, by Ginger
ɾƛ3Ḋ[kf|5Ḋ[kb works too, apparently
[AlanTheBagel] im trying ɾ(#{n15%n,}#{n3%¬kf,}#{n5%¬kb, but it errors with invalid if statement
19:30
@Ginger [that mac] no way
[that mac] did you just program in vyxal?
yup, it's the end of days
[AlanTheBagel] ?
@Ginger [user] i cant red
[user] carp
🐟
[RubenVerg] alright reshape wasn't as bad as I thought
[RubenVerg] I'll open a PR for a reshape element and if/after it's approved I'll make another one for APL-style ranges
@Bridget [that mac] (this)
19:58
RubenVerg pushed a commit to Vyxal/v3-reshape in Vyxal/Vyxal: Add reshape function & ÞR element
RubenVerg created branch v3-reshape in Vyxal/Vyxal
RubenVerg opened pull request #2069 (Add reshape function & ÞR element) in Vyxal/Vyxal
github-actions[bot] pushed a commit to Vyxal/v3-reshape in Vyxal/Vyxal: Scalafix changes
[RubenVerg] I hope the code is clear enough, I tried to make it as readable as I could
20:11
my server (and both bots) are offline
not sure why yet
in The Sand Trap, 3 mins ago, by Rydwolf Programs
My parents probably unplugged it
so it'll probably be a little while until they're back
 
1 hour later…
21:41
me omw to do more star canceling
 
1 hour later…
23:07
@Ginger so the syntax is going to need to be changed
meaning it'll be a 3.5 feature

« first day (1369 days earlier)      last day (406 days later) »