Because I feel like half of version 3 development has somewhat been "hey I found this cool library/framework" of "what about this idea that completely breaks a lot of things" and then you figuring out how to handle them
I have not figured out how to do symbolic stuff, and the only breaking idea you had that I can remember is the modifiers that couldn't be parsed normally, which you figured out yourself with the new non-parser-combinator parser
I think for the Sympy replacements, we could just do approximations with numeric methods for most of them and call it a day
I just realized I've never used anything but the most basic of unit tests before
I should try out integration tests and different styles of tests (property tests like you suggested, for one)
Exhibit a: "hey can you create a prototype of how vyxal as scala would work?" VyxalS. Exhibit b: "hey look at this cool parsing library let's make that work for all sorts of non-combinatorial structures" a pretty good attempt at making things like structure closing work. Exhibit c: "hey I'm gonna rewrite the docs for a lot of things in v3" you go ahead and graciously write a lot more detail than I had
Also, there's all the tiny little style changes you suggest on my horrible scala + all the times I have scala questions you answer them
@lyxal You mistake my intent there - I make those little changes not because I want to help you learn, but because I am a pedant and an idiom nazi and I want to show my superiority to people :P
To be honest, I kinda feel bad for pushing you to use Scala for v3, because it seems like moving from Python to a less mainstream language (and a compiled one, at that) is going to make it harder for people to contribute
Ginger even said they'd probably step away once v3 hit
Nim would've been cool, somewhat close to Python in terms of syntax, extremely flexible syntax, chock full of features. Just somewhat buggy and not that well supported
@user you gotta wait two minutes before you say this stuff :p (also for some reason Edge's spellcheck didn't say that was wrong, which is weird because it's usually pretty good about that stuff)
You're going to hate me for this, but now that we don't have global variables, what if we...tried splitting everything up again...haha, just kidding...unless...?
We do have to keep in mind that Vyxal v2 transpiles to Python, which does JIT and all that fancy stuff, while we're interpreting Vyxal ourselves in v3. That said, Vyxal is a simple enough language that it shouldn't matter
basically it works well for long-running stuff (for example it's REALLY good at raytracing, it's like 40x faster than CPython) but not short things like Vyxal
I am new to Scala and currently trying to work with the play framework.
This is working code I wrote:
def authenticate = Action (BodyParsers.parse.json) { req =>
req.body.validate[AuthenticationForm].map {form =>
UserRepository.findByCredentials(form).map { user =>
user....
Suppose you want to write a parser to parse a file. If it succeeds, you want to get an AST object representing the parsed code. If it fails, you want to get a string containing an error message. That's where Either comes in. Your parser can return an Either[String, AST], so that if it succeeds in parsing, it returns a Right containing the AST, and if it fails, it returns a Left containing the error message
Unlike Python, Scala can't really use the same variable for AST and String, so Either is used for that. You can make a variable val x: Any that can hold ASTs and Strings, but it can also hold anything else, so you lose the type safety (Scala 3 does have union types but because of erasure on the JVM, you can't check whether, say, a value of type List[String] | List[Int] is a list of strings or ints at runtime)
Exceptions are a lot more convenient when there are multiple kinds of errors you could get and you don't want to have an Either[ERror1, Either[Error2, ...]
It'd just be a little long, but maybe the command itself could be called wmill or something
What do y'all think about supporting two build systems, one slightly annoying to use but with better docs and support, and the other easy to use but with poorer docs? Worth the effort to see if the second one gets better eventually?
PS C:Documents\vyxal> mill fastLinkJS
mill : The term 'mill' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the
name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ mill fastLinkJS
+ ~~~~
+ CategoryInfo : ObjectNotFound: (mill:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Suggestion [3,General]: The command mill was not found, but does exist in the current location. Windows PowerShell does not load commands from the current …
./mill jvm.assembly and ./mill fastLinkJS seem to work, and when you open index.html in your browser and open up the console, you should be able to run Vyxal.execute.
I've got loop inside lambda and need recursive call lambda from the loop. But in this code λ...[...| x]..; "x" means continue loop. How to make lambda call in that place? Thank you!
Btw, it turns out sbt can be run without the shell, you just need to use the --client option. I just wasted like 5 hours trying to make my own sbt client when it's existed this whole time
You can just do sbt --client compile or whatever without dropping into the shell
Mill will let you use a nicer project structure and is supposedly less complex, but the current level of nesting isn't that bad and we don't care if sbt is more complex since it's got way more documentation and we're not doing anything advanced
Salacious Bacon Tripod
code-golfrandomstring
In a certain chatroom, we like making acronym jokes about the build tool we use called sbt. While it usually stands for "Scala Build Tool", we aim to come up with all sorts of meanings, such as:
Stupid Brick Teeth
Sussy Baka Training
Shady Blue Touris...
I am new to Scala and currently trying to work with the play framework.
This is working code I wrote:
def authenticate = Action (BodyParsers.parse.json) { req =>
req.body.validate[AuthenticationForm].map {form =>
UserRepository.findByCredentials(form).map { user =>
user....
