« first day (1324 days earlier)   

12:28 AM
@Ginger deltarun refencen!?!?!?!?!?
 
[Ginger] mmmmmaybe
 
dang, implementing prime number stuff is harder than i thought
mostly because there's no sympy i can use :p
and spire only provides prime checking for longs
 
1:00 AM
Hello, I've been summoned by emanresu
 
[lyxal ♦️] Hi
 
Let me find a link to a prime test alg I implemented a while back
It's rabin-miller which is quite fast but also nice and simple
 
@tybocopperkettle [Ginger] hello
@tybocopperkettle [lyxal ♦️] looks simple enough to port to scala
 
Yeah it should be easy
 
ah, it uses pow
mm that's gonna be fun
 
1:07 AM
That's also fairly simple to implement
 
ik it's just a bit more tedious
also, just realised the random.randrange part might be a problem
although I guess that's a larger scoped problem anyway
 
Could also port the sympy alg although it's quite a bit more complicated
And pow's like 10 lines to implement, 5 if you don't care about it being O(n)
 
[Ginger] does scala not have a pow builtin???
 
@emanresuA that gets into bitshift territory
@Bridget it probably has one in the scala stdlib math library
 
@Bridget Modpow is needed
 
1:09 AM
but the problem with that is that it only will work for longs at most
 
Can you not bitshift bigints?
 
it gets complicated
 
I think you can in JS, not sure about scala
 
Can replace it with floor division by powers of 2 then
 
last time we tried to do bitshifting of bignums it was a bit painful
anyhow, all this still comes with the problem of random.randrange
more specifically that the stdlib Random class only provides between for Longs at most
and spire's random section also only provides for Long
 
1:50 AM
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Add untested nth prime
github-actions[bot] pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
 
[Ginger] I'm gradually becoming more convinced that the bot's re-revamped architecture is too general
[Ginger] because it leads to stuff like the square brackets in that commit message being needlessly escaped on Discord
[Ginger] also can someone pretty please review the discord pr
 
later - i'm working on a prime test function which has led me to port python's random library to scala
 
[Ginger] it do be like that, far too frequently
 
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: modpow?!?!
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Merge branch 'version-3' of github.com/Vyxal/Vyxal into version-3
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: modpow?!?!
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Merge branch 'version-3' of github.com/Vyxal/Vyxal into version-3
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: PRIME
 
2:07 AM
That took way too long
 
github-actions[bot] pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
 
Just in case anybody knows of a command that, no matter what, would only be used at the end of a program, ' followed by EOF gets interpreted as a command
 
2:41 AM
@tybocopperkettle [user] You can in Scala yeah
 
3:01 AM
AMiller42 pushed a commit to Vyxal/parser-error-handling in Vyxal/Vyxal: Handle modifiers missing arguments
 
 
1 hour later…
4:27 AM
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Add set diff/is prime/n-th prime/quine cheese/change join-ons to be quote things
github-actions[bot] 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: Set XOR
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Update tests
github-actions[bot] 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: Update tests.yaml
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Merge branch 'version-3' of github.com/Vyxal/Vyxal into version-3
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Update tests.yaml
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Merge branch 'version-3' of github.com/Vyxal/Vyxal into version-3
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Update ElementTests.scala
 
4:51 AM
room topic changed to Vyxal: For discussion about Vyxal. Repo: github.com/Vyxal/Vyxal | Org: github.com/Vyxal | Interpreter: vyxal.github.io/latest.html (v3) OR vyxal.pythonanywhere.com (v2) | Discord: discord.gg/N9AfEF9zz5 [actually-12-now] [chat-bot] [code-golf] [dank-memes] [discord] [epic-gamers] [joe] [never-gonna-give-you-up] [powered-by-copilot] [rickroll] [short-programs] [too-many-tags] [unicode] [vyxal] [vyxal-bot-2] [we-currently-have-11]
 
5:02 AM
AMiller42 pushed a commit to Vyxal/parser-error-handling in Vyxal/Vyxal: Update tests
 
5:26 AM
I'm noticing that in the REPL, something like "abc"3i will wrap around when indexing out of bounds, whereas in the online interpreter, it errors. Is that just due to Java and JS differences, and if so, should we fix that?
For reference, Vyxal 2 behavior was to wrap around
 
it's fully intended to wrap around
lst(Math.floorMod(ind, lst.length))
the joys of cross-compatibility :p
 
oh you know what, it is wrapping around for lists, but not for strings
 
???
that shouldn't be possible
strings are cast to list before indexing
 
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Make strings iterable as lists, not indexed seqs
 
5:32 AM
that might fix it
 
how does one listify a string? i.e. "abc"🍪 returns ["a", "b", "c"]
 
f
 
I'll take the f, because I should've remembered that
but instead i forgor 💀
 
[that mac] 💀 💀 💀
 
 
2 hours later…
7:31 AM
[user] Funny, why do IndexedSeqs not work?
 
Scala.js must implement them differently
The stack trace was mentioned indexedseq methods
Which is what the underlying VList value of a iterablified string is
 
[user] But what could it possibly do differently? Length?
[user] I don't understand why List works but not IndexedSeq specifically
[lyxal ♦️] It's patched on the main site, but the error is preserved on the v3.0.0 site
[lyxal ♦️] Try it Online!
@Bridget [lyxal ♦️] Oddly, it works on jvm, but not js
[lyxal ♦️] Allegedly
[user] This is wild
[user] Math.floorMod may be part of the problem if there's discrepancies between JVM and JS
@Bridget [user] Also I love the fact that we now have versions so much
@Bridget [lyxal ♦️] It wasn't happening with standard lists
[lyxal ♦️] Those wrap around as intended
[user] Does L on strings do weird stuff in the unpatched version?
[user] L is length right?
[lyxal ♦️] Yeah
[user] On phone so can't check
[lyxal ♦️] It behaves normally
[user] Huh
[lyxal ♦️] Try it Online!
[lyxal ♦️] Returns 3
[user] So the only possible thing is the apply method of List and IndexedSeq
[lyxal ♦️]
 $c_sci_ArraySeq$ofRef.apply__I__O (internal-b4e3282ff5c....js)
[lyxal ♦️] I know the underlying iterable is an indexed seq because that's what metals says is the result of
[user] Yeah ArraySeq extends IndexedSeq
[user] Perhaps ArraySeq is backed by a JS array in Scala.js and that screws it up somehow?
[user] Gonna investigate tomorrow
 
 
3 hours later…
11:16 AM
[lyxal ♦️] I found the problem
[lyxal ♦️] Trying to index out of bounds in a gives a
[lyxal ♦️] Trying to index out of bounds in a / gives a
[lyxal ♦️] The method uses to detect an out of bounds index
[lyxal ♦️] JVM seems to treat the two errors as the same error type
[lyxal ♦️] JS otoh doesn't
[lyxal ♦️] It seems to be that in Java, extends
[lyxal ♦️] so ofc jvm is going to recognise the specialisation as an instance of the regular one because that's how polymorphism works. Fundamental oop
[lyxal ♦️] Scala.js doesn't seem to respect the inheritance chain
[lyxal ♦️] or at the very least, related objects are considered separate to the rest of the collections
 
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Catch both exception types for out of bounds
 
12:18 PM
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Why is it always [2, 1]?
github-actions[bot] 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: Add the element name to tests
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Merge branch 'version-3' of github.com/Vyxal/Vyxal into version-3
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Add the element name to tests
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Merge branch 'version-3' of github.com/Vyxal/Vyxal into version-3
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Add edge case for ^_f.
github-actions[bot] pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Scalafix changes
 
12:38 PM
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Add palindromise
 
github-actions[bot] pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
 
16 hours ago, by Fmbalbuena
What's the equivalent of in Vyxal 3?
can you do ^ too while you're implementing elements?
 
gonna be hard to find a one byte spot to put it
 
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Make palindromise Ḥ instead + untested multi-set diff
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Merge branch 'version-3' of github.com/Vyxal/Vyxal into version-3
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Make palindromise Ḥ instead + untested multi-set diff
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Merge branch 'version-3' of github.com/Vyxal/Vyxal into version-3
github-actions[bot] 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: Implement remove-at-index
 
12:56 PM
@Fmbalbuena Q
 
[Ginger] hello
 
 
[Ginger] whar
 
nice delete detection there
 
[Ginger] get rulered
[Ginger] :sus:
[lyxal ♦️] now that's a skill issue on the bridge's part
[lyxal ♦️] that's less than 2mb even imgur can handle that
[Ginger] it's a skill issue on chat's part
 
12:59 PM
github-actions[bot] pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
 
[Ginger] the messages aren't being sent because Discord's CDN URLs are longer than 200 bytes
[that mac] lul
[that mac] imgur them
[Ginger] this is why I tried (and failed) to implement a link shortener earlier
@Bridget [lyxal ♦️] the url for the image I sent is 106 bytes
@Bridget [Ginger] I actually might, depending on how chat handles imgur uploads
@Bridget [Ginger] add the length of the filename
[lyxal ♦️] included
[lyxal ♦️]
[lyxal ♦️] 106 bytes
[Ginger] wrong URL
[lyxal ♦️] then strip the query parameters idiot
[Ginger] which gets rulered even without a filename
[lyxal ♦️] not rulered
@Bridget [Ginger] well I don't know if they're useful or not
[lyxal ♦️] they're not
[lyxal ♦️] the image still renders
[lyxal ♦️] and it'll even onebox in chat
 
 
[lyxal ♦️] I always strip them
[Ginger] I'm going to try using imgur, since IIRC Discord CDN links expire now
[lyxal ♦️] oh
[lyxal ♦️] so that's what the query parameters are for
[that mac] ?
@Bridget [lyxal ♦️] my money's on whatever image uploading solution SE comes up with
[lyxal ♦️] which I guess it will have to be actually
[lyxal ♦️] now that I think about it
[Ginger] that's not happening yet, and I intend to still be around in April 2024 to switch it over :p
[lyxal ♦️] oh dang that means the paste to upload userscript(s) are going to need updating
[Ginger] probably not
[Ginger] they hijack the normal upload button code (in a really cursed way), so they'll still work most likely
[lyxal ♦️] assuming the layout isn't changed
[lyxal ♦️] SE is going to have to shudders update chat for this
[lyxal ♦️] who knows what they'll touch
[Ginger] likely just the backend
> [lyxal ♦️]
> image hosting by imgur.com
[lyxal ♦️] they're gonna have to touch chat
[Ginger] chat image uploads POST to a chat endpoint (which I think is a relic of when you could upload arbitrary files to chat), so they'll probably just change that
[Ginger] and remove that subtext ig
[lyxal ♦️] as well as the imgur logo
[lyxal ♦️] and that might even lead to a partial redesign of the classes/ids involved
[lyxal ♦️] I hope when they make the imgur changes enough is learned about how chat works to have more devs available to work on it
[Ginger] :doubt:
[Ginger] it's probably best if they change as little as possible with chat
 
I don't mean to change chat
I mean so that more people even know how to
You know how we always make the joke "at least 3" when we're talking about an obviously large number? Well the number of devs who know how to change chat yet alone access it is roughly "at most 3"
Don't quote me on that though
 
 
2 hours later…
2:59 PM
> [Ginger]
> You know how we always make the joke "at least 3" when we're talking about an obviously large number? Well the number of devs who know how to change chat yet alone access it is roughly "at most 3"
[Ginger] heehoo
 
 
4 hours later…
6:59 PM
!!/status
 
@Ginger I am doing undefined.
 
again? smh
 

« first day (1324 days earlier)