« first day (1733 days earlier)      last day (42 days later) » 

00:30
lyxal pushed a commit to Vyxal/v3-codepage-sensibility in Vyxal/Vyxal: Swap in missing chars
lyxal pushed a commit to Vyxal/v3-codepage-sensibility in Vyxal/Vyxal: Merge branch 'v3-codepage-sensibility' of github.com/Vyxal/Vyxal into v3-codepage-sensibility
github-actions[bot] pushed a commit to Vyxal/v3-codepage-sensibility in Vyxal/Vyxal: Sort elements in test file from recent commit
00:43
lyxal pushed a commit to Vyxal/v3-codepage-sensibility in Vyxal/Vyxal: Silly little lexer bug
github-actions[bot] pushed a commit to Vyxal/v3-codepage-sensibility in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
lyxal pushed a commit to Vyxal/v3-codepage-sensibility in Vyxal/Vyxal: update sbcs lexer again
lyxal pushed a commit to Vyxal/v3-codepage-sensibility in Vyxal/Vyxal: Merge branch 'v3-codepage-sensibility' of github.com/Vyxal/Vyxal into v3-codepage-sensibility
01:01
lyxal pushed a commit to Vyxal/v3-codepage-sensibility in Vyxal/Vyxal: Update SBCSLexer.scala
 
11 hours later…
11:41
lyxal pushed a commit to Vyxal/v3-codepage-sensibility in Vyxal/Vyxal: Better support for two char # modifiers
11:59
lyxal opened pull request #2141 (Codepage Shuffle v3.5 edition) in Vyxal/Vyxal
lyxal pushed a commit to Vyxal/v3-codepage-sensibility in Vyxal/Vyxal: Update codepage.md
lyxal pushed a commit to Vyxal/v3-codepage-sensibility in Vyxal/Vyxal: Update codepage.md
12:14
lyxal merged pull request #2141 (Codepage Shuffle v3.5 edition) in Vyxal/Vyxal
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Merge pull request #2141 from Vyxal/v3-codepage-sensibility
lyxal deleted branch v3-codepage-sensibility in Vyxal/Vyxal
well if version redirecting to latest doesn't matter anymore, I might as well make a release now so code.golf and byte heist can get the remidied vyxal versions
when someone asks me how many extra codepage slots there were:
in The Nineteenth Byte, yesterday, by ATaco
@lyxal Eight!
@lyxal it feels so good knowing I don't have to also bump the string in Interpreter.scala to some prediction of what next release will be
freeing, even
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Bump build.sc to have version 3.5.1
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Merge branch 'version-3' of github.com/Vyxal/Vyxal into version-3
I know re-releasing 3.5.0 was suggested, but I'd prefer it to be 3.5.1
github-actions[bot] pushed a commit to versions/main in Vyxal/versions: Push new version files.
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Fix a quick little oopsie
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Remove an extraneous element definition
github-actions[bot] pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
12:35
6 messages moved to ­Trash
github-actions[bot] pushed a commit to versions/main in Vyxal/versions: Push new version files.
lyxal created tag v3.5.1 in Vyxal/Vyxal
release fr this time
[noodle man jacob] Rad
@Ginger [lyxal ♦️] planning to clean that
[lyxal ♦️] had to hit re-release twice lol
lyxal pushed a commit to versions/main in Vyxal/versions: Remove duplicated 3.5.1
13:46
@lyxal the interpreter doesn't provide hover for ~
seems to be a problem with all modifiers
hmm
did you rename the modifier node in the grammar
the .grammar file?
yeah
no
at least, I don't think I did
I left the names the same
13:49
it doesn't look like ~ is listed as a modifier
ModifierChar {$[⑴⁜∦⎂⎇▦⑶¨~ᛞ⑵⟒¿∺⩔⑷Ẅ∥]}
AddModifier(
      symbol = "~",
      keywords = Seq("filter:", "without-popping:", "peek:"),
      numberOfElements = 1,
      ModifierOverload(
        name = "Filter",
        args = Seq("mon"),
        description = "Filter the top of the stack with #1",
        example = "#[1|2|3|4|5#] ~2≛ -> [2, 4]",
      ),
      ModifierOverload(
        name = "Peek",
        args = Seq("dyd+"),
        description = "Apply #1 without popping",
        example = "3 4 5 ~+ -> 3 4 9",
      ),
    ),
well yeah, the grammar isn't autogenerated
you gotta do that bit by hand :p
@Ginger well see it actually half is
the copy-paste part isn't automated (yet)
but the "generate the .grammar file" is
????? since when
okay yeah it looks like someone moved stuff around and broke it
Jan 8 at 3:40, by Vyxal Bot
lyxal pushed a commit to Vyxal/v3-new-3.5-ideas in Vyxal/Vyxal: Add the ability to auto-generate grammar files (SBCS for now)
13:52
ae
you...didn't see me making several commits to the website to test grammar changes on prod?
it occurs to me that we'll have to start having multiple grammars in order for unified versions to work correctly
@lyxal wow 2 releases in a single day?!11
yesterday, by lyxal
I think I'll be avoiding that
wild
let me try and fix the language configuration
@Themoonisacheese 1 release, deleted and re-released
@Themoonisacheese I meant the times I've done several different releases same day
13:55
!!/status
the problem seems to be that you made a bunch of stuff tokens
@Themoonisacheese I don't want to tell you what I'm doing. You smell bad. Go wash yourself.
that kind of thing where not even an hour passed between 3.4.4 and 3.4.5
13:55
oh wait no
@Themoonisacheese I can't believe moon is a token now
@lyxal you need to rename ModifierChar to Modifier
@VyxalBot newer status!
no way
@Themoonisacheese I am inventing a new type of communication device that allows people to communicate telepathically.
seems like VB is working correctly on gingersrv, so I'll move bridget over in a bit
13:57
you win some you lose some
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Update DocsUtils.scala
and then all the discord bots, and then lastresort will be empty again
@Ginger it'll autogen once workflows are done
gonna keep it around though since it's more powerful than gingersrv
!!/status tingly
13:58
@lyxal I-I-I a-a-am doing a runs away wewy wong and compwicated mathematicaw fowmuwa ♥(。U ω U。) that sweats wiww e-e-ewentuawwy wead to the d-d-destwuction wags my tail of t-t-the unyiwewse. glomps
"again" as if it wasn't filled by gnome3 to begin with
yeah I removed that I think
@VyxalBot most casual threat to destroy humanity
dunno if I'd call that "casual"
i swear the debian installer used to ask you if you wanted a DE at all
13:59
so I'm going to have to do some shenanigans to make autogen grammar work correctly
github-actions[bot] pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
because at the moment it's transpiled from Lezergrammar into JS during theseus's build process
but if it's generated by Scala that transpilation step has to happen at a different point
@VyxalBot copying time!
@Ginger it generates Lezergrammar
I think grammars will have to become part of the pages output for latest
yeah I was about to say that
14:00
and we add an extra step that pulls in the generator to run the transpiler
for archive we can do that during the archive workflow
there is an alternative solution: we do it on theseus's end by depending on the transpiler and transpiling the grammars on the user's computer during startup
lyxal pushed a commit to vyxal.github.io/theseus in Vyxal/vyxal.github.io: Update vyxal-lit.grammar
also we can nuke the generator for the keyboard, since that code no longer exists
keyboard?
14:03
yeah, the legacy element keyboard
its generator still exists iirc
it does?
yeah, same file as the theseus one
lol
just like all the other cruft in pages/ :p
modifier have hover now!
14:04
yay!
uh, it's a bit ugly :p
didn't expect HTML to be supplied
ah, it's a cursed combination of markdown and HTML
it's github markdown :p
that's on me for being lazy and reusing the function that makes modifier overloads
looks kinda bad on the site though
what shall we do about this
overload overloadToString(overload: ModifierOverload): String to have an option to generate nice text
which i will do at not 1;06am
[lyxal ♦️] Because it is bed now
right
gn
14:11
gingershaped pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Overzealous find/replace
github-actions[bot] pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
gingershaped opened issue #2142 (Missing/mismatched elements) in Vyxal/Vyxal
yeah I found another one :p
Σ this time
I'm gonna add them to that issue as I find them
@Ginger [lyxal ♦️] That's because there's two Unicode sigmas
[lyxal ♦️] That sounds brain rot but it really isn't
but of course
[lyxal ♦️] It exists
evidently we're using the wrong one somewhere
14:16
[lyxal ♦️] Something has the wrong character
again: we need tests for this stuff
[lyxal ♦️] Well see there would have been
[lyxal ♦️] But the test sorter would have removed the test
the what now
[lyxal ♦️] Because it filters by presence in the codepage
[lyxal ♦️] The yaml test autosorter
it filters all the tests??
we have a test framework right
should just be iterating over the codepage and the element list and making sure they're in sync
14:18
@Ginger [lyxal ♦️] No only the yaml file with the element tests
[lyxal ♦️] It would have originally had a test for sum, but it removes entries that aren't in the codepage
[lyxal ♦️] tests.yaml
sounds like a great source of footguns
[lyxal ♦️] The filtering part was mostly to remove the stuff from old codepage
@Ginger [user] Yeah I plan to do this today
thanks user
[lyxal ♦️] It could probably go back to just sorting without filtering
I'll fix this one by hand I guess
14:20
[lyxal ♦️] I'll get going then
[lyxal ♦️] o/
\o
the correct character appears to be
14:38
gingershaped pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Fix ∑ using the wrong character
fingers crossed
github-actions[bot] pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
15:19
!!/status
@Themoonisacheese I am working hard... or am I hardly working?
15:44
btw @lyxal i assume v3.5 breaks vyncode?
[user] Yeah
16:00
[the cat] I think I'm going to spend the next little while writing a spec for theseus
[the cat] because as it stands I don't think I can hold all of its functionality in my head at once, and I need to do a lot of refactoring to make Unified Versions a reality
i don't understand how unified versions is so complicated
/gen
does thesesus currently not associate editing to versions?
[the cat] theseus does a lot of things
[the cat] that is in fact the problem
my logic is that as far as running vyxal code, pyvyxal taught me that if you can get to vyxal.execute(), you're golden
[the cat] the issue is that when I originally wrote it a year or two ago I didn't really know what I was doing, so it's A Mess
so i assume the problem must lie in the editor?
16:04
[the cat] same story with Vyxal Bot, in case you're wondering why I rewrote it four times
i think that'll always be the case
you can go look at my fucking mess from 2 years ago if you want to feel better about you programming abilities github.com/themoonisacheese/2bored2wait/blob/master/main.js
[the cat] let me rephrase, then: I don't want to try and implement unified versions on the current codebase, because I'll spend a month doing it and the result will be a dumpster fire
ah.
el classico "this codebase is such a mess i'd rather be writing documentation"
[the cat] so what I'm going to do is write a spec, and then use the spec to rewrite everything
good luck i guess
time for me to go home
16:07
[the cat] even if that takes longer than just going for it, it'll be better for my mental health
@Themoonisacheese I miss my wife. Some hedgehog flirted with her and now she's left me for the animal.
[user] image.png
[the cat] ayyy
"i'm back in the fucking building again!"
ysthakur pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: test: Add ElementInfoTests
16:08
@Themoonisacheese [user] It's usually called a brothel
@Bridget [user] Yeah making a spec makes sense
[user] Also much lessl ikely you'll write some code, realize you actually want to change the design completely, and then rewrite all of that code
[the cat] one of the problems with the interpreter codebase is that the bits where reactive code and procedural code interact are really not great
[the cat] so I'm going to try and nail down exactly how things are supposed to behave if, say, you delete an input group while it's being run
[user] 👍
[the cat] also I'm going to replace our webpack monstrosity with nextjs, since we don't actually need it anymore
ysthakur pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Rename kb to kd in ElementInformation
github-actions[bot] pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
ysthakur pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Document #~ (Call Without Popping)
github-actions[bot] pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
16:38
ysthakur pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Make ⎊ the Map Over Permutations element rather than ⧖
[user] Our life would be much easier if this SIP were implemented: docs.scala-lang.org/sips/alternative-bind-variables.html
[user] It would allow us to do stuff like case (n: VNum, fn: VFun) | (fn: VFun, n: VNum) => rather than write two separate match arms with duplicate code
github-actions[bot] pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
[user] Seems abandoned though :(
[user] ???
17:10
[user] @!lyxal It turns out that both l and have an overload that takes a function and a value and repeatedly applies the function to the value until the fixpoint is reached
[user] And (which is the only undocumented element left) has an overload that does the same thing, but doesn't include the initial value
[user] @!lyxal Another thing: also has overloads for splitting lists, strings, and numbers into n chunks. It treats strings as lists, though (it uses ListHelpers.intoNPieces rather than StringHelpers.intoNPieces). But there's also Þ÷ , which works only on lists and strings and uses StringHelpers.intoNPieces for strings. And there's ÷, which only does this for strings
17:29
ysthakur pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: test: Ensure keywords aren't duplicated
ysthakur pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Slightly simplify MiscHelpers.untilNoChange
17:42
here's the hackmd so far, what do yall think?
[user] Needs a little fleshing out tbh
[user] image.png
[user] I like the hand though
amazing
fixed
[user] Looking much better now 👍
[user] "Stuff" is...not a great word to use
I mean, currently they're called "things" internally :p
[user] o.O
17:47
ThingCard and whatnot
[user] Amazing
[user] Looks good
[user] Are you not going to describe the interaction between the Scala.JS interpreter code and the UI code in there?
[the cat] that's an implementation detail, if I do describe it it'll be in a different document
 
2 hours later…
19:51
@lyxal peek is behaving weirdly
20:09
[user] How so?
[the cat] it uh
doesn't seem to be peeking
[user] That's
[user] not helpful
[the cat] I am on mobile right now :woohoo:
[user] Oh
[user] mb
[the cat] I'll provide a more useful complaint in a moment once I'm at a machine with a keyboard
[user] Thanks
[user] No rush
[the cat] also I'm not really looking forward to redoing Theseus lol
[the cat] at least maybe yall can help since I'll have a spec this time
20:31
[user] Huh, she finally ran out of energy
[user] I was wondering when that would happen
@Bridget [user] 🫡 will need some guidance from you (a list of tasks or something) but yes, I will I try to help
[the cat] :tbh:
[the cat] too tired to come up with anything concrete today but I'll work on the spec more tomorrow
[user] 👍
@Bridget [user] Do you have autism btw?
[the cat] let me put it this way: I'm not diagnosed with it :p
[user] lol
21:24
@Bridget requires 2 dyads
[RubenVerg] it should be that if the first one is a monad it calls it with just the left argument
[RubenVerg] dup dip:F G i guess
Would that not just be F G?
[RubenVerg] no, it's a hook
[RubenVerg] infix would be (F x) G x
[RubenVerg] G(F(x), x) if you prefer
That's just dup
[RubenVerg] just like if F is a dyad it's G(F(x, y), y)
@lyxal [RubenVerg] yeah but that's not an unit
[RubenVerg] it's the reasonable case for left fork where the first function is a monad
21:35
Grouping modifier
[RubenVerg] that's way longer?
[RubenVerg] okay not way
[RubenVerg] just longer
It's still just a single modifier
[RubenVerg] what else would you make left fork monad dyad mean?
Well that's why it's undefined thus far
@Themoonisacheese v3 "broke" it
Not that it'd make sense anyway
It's trained in v2 answers
@lyxal [RubenVerg] Uiua
[RubenVerg] though anyways, "parse error please tell this to vyxal devs" is a pretty bad error message for "this modifier does not support these arities"
21:39
Yeah, no clue why it isn't throwing an error like elements do
I'll look into it later
@Bridget having ÷ and one other element is intentional
Two, well that'll need consideration as to whether the string behaviour is enough of a distinction to want to keep
Although one is a digraph simulated by two characters without it
Okay then, list digraph ÷ can go
@Bridget no reason it shouldn't be
Just tested 3 5 ~+W and it produced [3, 5, 8] as expected
[the cat] I forgor
Were you using it with a monad?
22:46
@lyxal [user] Why's that?
[user] I'd like it if ÷'s string-num overload replaced string-num overload, making room for a new overload for ÷
@Bridget vectorising overload and non-vectorising
[user] Ah
[user] Do you often need to vectorise chunking?
don't know, but it's good to have imo
[user] 👍
AddElement(
  symbol = "⎊",
  keywords = Seq("map-permutations", "map-perms"),
  arity = 1,
  Options(
    vectorises = false
  ),
  Overload(
    name = "Map Over Permutations",
    args = Seq("any", "fun"),
    description = "Map {#2|#1} over all permutations of {#1|#2}",
    typeSwitchable = true,
  ),
),
huh?
that doesn't make any sense
is syntax
That makes no way to call the built-in with a function
22:54
[user] It's in Elements.scala
I know
[user] I assumed you were moving the hourglass element's any-fun overload to ⎊
⎊ shouldn't be in there
that's an accident if it's in there
[user] Uh oh
could be left-over from when I was still thinking of whether to do the quantum stuff
22:55
[user] I'll put it back into the hourglass then
:+1: because otherwise there's no element form
@Bridget [user] @!lyxal Also, what do you wanna do about this?
[lyxal ♦️] looking into
[user] I haven't documented 's fixpoint overload yet
[lyxal ♦️] having fixed point without initial value is 100% correct
[lyxal ♦️] that's intentional
[user] Cool I'll document it then
[lyxal ♦️] l and , on the other hand
[lyxal ♦️] ohhh I see what I was going for I think
[lyxal ♦️] I think I meant to have a "return only last value" variant
[user] Ah that makes sense
[lyxal ♦️] but evidently, I forgot the "last value" part
[lyxal ♦️] is last value
@Bridget [pacman] does one return every value and the other only return the fixpoint
[pacman] oh yeah
[lyxal ♦️] when I say it is, I mean that's the one that will be
@Bridget [user] Okay I'll make it do that rq
[pacman] is fixpoint different from unique values
[lyxal ♦️] no I did
[user] Also bot ded I guess
@Bridget [user] Oh ok
[pacman] i.e a->a rather than a->b->a
[user] Yeah
[user] You only compare to the previous value, rather than to all the previous values
[user] If I'm understanding you right
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Make return only the last value
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Merge branch 'version-3' of github.com/Vyxal/Vyxal into version-3
[pacman] well a fixpoint should also watch out for loops
[pacman] but yes
[user] I don't think that's the usual definition of fixpoint?
ysthakur pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Remove ⎊ from Elements again
ysthakur pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Merge branch 'version-3' of github.com:Vyxal/Vyxal into version-3
23:04
[pacman] unique values for cos(x) would go from 0 to pi/2
[pacman] whereas "fixpoint" would go from 0->2pi
[pacman] idk im just thinking of something with periodicity 4 or something where a sequence alternates between 0 and n where n>0
[user] The fixpoint of cosine is this thing: mathworld.wolfram.com/DottieNumber.html
[user] Not 2pi
[pacman] right thats why its in quotes
github-actions[bot] pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
[pacman] oh this is recursively applied
[pacman] duh
[pacman] periodicity would be a cooldigraph
[user] +1!
[user] Probably useful somewhere
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Update ElementTests.scala
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: Mitigate weird testMulti issue without spending braincells
ysthakur pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Document fixpoint overload of ⧢
ysthakur pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Resolve merge conflicts
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Better exception for when modifier given elements with arities the modifier doesn't support
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Update Modifiers.scala
ysthakur pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: test: Simplify ElementTest for ℂ
ysthakur 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: Scalafix changes
github-actions[bot] pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit
23:22
[lyxal ♦️] going to add bitwise ops as digraphs now
[pacman] oh can you add all the vyxal 2 string constant digraphs
[pacman] a ton of the bracket ones are useful
[lyxal ♦️] certainly
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Add the 4 missing bitwise ops as digraphs
lyxal pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Merge branch 'version-3' of github.com/Vyxal/Vyxal into version-3
now for the string consts
ysthakur pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Simplify a couple implementations
ysthakur pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Merge branch 'version-3' of github.com:Vyxal/Vyxal into version-3
pfft we keep interrupting each other's commits lol
[user] lol yeah I'll hold off until you're asleep
[user] I don't have much to do besides throw in some doc comments here and there
23:34
github-actions[bot] pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Sort elements in test file from recent commit
@Bridget that's like 14 hours from now :p
it's 10:34am
[user] Bit impressed by that workflow, the fact that it works
@lyxal [user] Well, until you're away from Vyxaling, at least :P
(VList | VStr | VNum) == VPhysical btw
[user] Ohh
github-actions[bot] pushed a commit to Vyxal/version-3 in Vyxal/Vyxal: Refresh element and/or trigraph docs from recent commit

« first day (1733 days earlier)      last day (42 days later) »