and vyxal is still primarily a golfing language, it isn't really readable as far as the average language goes, it's just more mnemonic than most golf langs
@hyper-neutrino for some reason I have the urge to pin that message
@Ausername What's the proper capitalization of Vylight? Vylight or VyLight?
I've noticed a few bugs with Vylight, as well as a couple bugs introduced by the Vylight integration, so I added a new issue label to help us keep track of them.
@user I think this this could be a good idea, though I have no experience with Github organizations, so I have no idea how people's current permissions might change.
@hyper-neutrino Nice! Mine greedy-matches the longest it can take - I honestly thought that was optimal but I never thought about stuff like that. How does yours work?
@Ausername it uses a dynamic programming state - builds an array of length N+1 such that the element at index x is the optimal way to represent the first x characters
and then it scans right, each time adding a new character by looking back and checking all possibly y such that [y:x] is a word and concatenating it to DP[y] and finding the minimum
if we encode the dictionary into a suffix trie this could be faster but it really doesn't matter unless your string has like a couple thousand/million chars lmao
@lyxal I probably should've asked but TBH I didn't actually consider myself a contributor to this language until quite recently :p
Also @lyxal I have upgraded username's better compressor to an optimal compressor TM; can I merge that into the built-in for string compression? just as a warning though, it apparently gets a bit slow on longer strings (though I'm surprised it's slower than username's, which is quadratic) but it should be 100% guaranteed optimal
also possible bug/unintended behavior: when you ctrl-enter to run the program immediately after collapsing/expanding an input field, it will toggle it again. this is easy to fix; just want to confirm this isn't intended right?
