@user Because it mutates the context's stack, and foo.bar is used for stuff that's just a property access (like ctx.peek). The convention is to use foo.bar() if bar mutates something
Because it's a top secret playground. If it fails spectacularly not many will know about an attempted extremely complex kinda-no-point-in-making-it golflang
Although my current indications are that it'll be public very soon
The infrastructure I built for it is making it so much easier to handle modifiers
!!/issue Add JSON parse elementUseful for JSON-related challenges. Already exists in Jyxal. Maybe make it øJ` for parity with Jyxal` element requestdifficulty: easy
LOAD COOKIES FROM "COOKIES.DB"; REMOVE EVERY COOKIE OF COOKIELIST OF COOKIES; WHERE NOW OF TIME; MINUS AGE OF COOKIE; LIKE NUMBER IS MORE THAN MAXAGE OF COOKIES;; DUMP COOKIES TO "COOKIES.DB";
!!/issue Add JSON parse element Useful for JSON-related challenges. Already exists in Jyxal. Maybe make it øJ for parity with Jyxal element requestdifficulty: averageenhancement
I know no one's contributed to Jyxal yet but I'll be done with school after May so if you yell at me I'll implement some stuff (without taking the bounty because I don't really want/need it) :)
IntelliJ Ultimate is paid and has a few extra features that you don't really need unless you're a professional, and you can get free access to it if you're a student
It might screw with the pre-existing messages because chat will just insert them according to their time and then there'll be two conversations at once
i suppose it isn't really just a general off-topic though. we could honestly split vyxal into an on-topic / actual work room and just a general chatter room?
anyway, i guess another solution is just to accept off-topicness as long as nothing important is being discussed, though that does make it harder to backread. @lyxal what do you think