Rule of FreeCell only allows to move one card each time, but it's possible to move a few using empty free cells and columns.
Each time, one card can be moved to an empty free cell, an empty column, or a column which the top card is one larger than this one. We can see that these empty area allow ...
You're expected to plug in the quadratic formula and work out both solutions, or your teacher actually intended to write x^2+1/x^2 instead but made a typo
@pxeger Thanks, it seems to be working almost perfectly! There's a couple weird things: it appears to be run as a worksheet when there isn't a main method (which is a great feature as long as it's intended), and it's a bit slow (which might be because it uses sbt instead of scala directly). I'll look into the latter, but this is amazing. Thanks again
@user yes it's intended; it basically just runs scala <code_file>, and scala tries to guess what kind of file you want. You can add -howtorun=script or whatever to the Options to force it to change behaviour.
@user and I don't think there's much I can do about it being slow; it's similarly slow on my desktop computer so I think it's just compiler and JVM overhead
It feels more like a joke language when the creator is threatening to turn it into MGS, except that it actually has a following because it's (supposed to be) a normal golfing language
They're good for languages with strict I/O requirements, and they make it easier to change behavior instead of having different builtins for slightly different functionality
Control of my CGCC account isn't in my non-existent will, so does that mean the UK government gets my account after I die? Does it go to my next-of-kin? Who knows? :P
How to become a rich Texan: 1. Travel outside Texas (probably the hardest step given how big Texas is) 2. Buy fruits 3. Go back to texas to make food bigger 4. Sell at profit 5. ???
@PyGamer0 btw, return sounds very odd for a lisp. If you're going for functional programming, I'd recommend having the last expression be returned implicitly, like in Scala
> If you use that interpreter behavior, even without a flag, to cast that data structure to a string output for something like a kolmogorov complexity challenge, I'd consider it cheating
Like Jelly's smash printing? That's a interpreter behaviour which deliberately modifies the output representation, and is often very useful in fixed-output challenges
Rather, let's just depend on people to not upvote "cheaty" answers like that. If someone says, "Ha, I beat your Vyxal answer using all of these flags," we call them out. That's all we need to do
> There is one exception, which is if the language specification specifically states how the [data structure] will be cast to a string, and requires that it is done when outputting. In this case, you would only ever be able to use the language for challenges which accept that format of string as output, and you can no longer claim that string is a [data structure].
@user Of course, that's exactly what I'm going to do
This is just my opinions on flags, I'm not trying to push for any sort of change in the rules
@RedwolfPrograms Smash-printing doesn't convert to a string. If you print halfway through a program, it'll still smash-print, but the original data structure will be returned
@RedwolfPrograms Not really, the changes in behavior are often really, really minor. A branch isn't the right place for different behavior anyway, flags or not
Lyxal has stated more than once that if flag scoring was changed, they would make a ton of Vyxal offshoots that each have a permutation of the flags built in. Basically like MGS.
