Argon VS pest

There have been several changes in Argon during the month of February, I completed the socket support and improved the IO on file, added a new library in Argon language but above all I added the generators (and other things, like atoms)

As planned, in the last month I managed to add support for network sockets to the Argon language. Support is not yet complete but you can use most of the features on both Linux and Windows. Also, several errors have been fixed. The current month will see me busy completing support for the socket module and continuing with the introduction of new libraries (probably the next module will be about Regex)

In December we were left with the implementation of multi-threaded support and now, it is finally possible to spawn more than one thread within Argon.

And some related parser tools: - https://github.com/kevinmehall/rust-peg - https://github.com/pest-parser/pest - https://github.com/lalrpop/lalrpop

I had recently completed the first year of my Computer Science class at school and will begin my second year soon. My schools' class forces the use of Java programming language, and I absolutely hated it. So, over the course of a little less than a month, I wrote my own programming language, in Rust (objectively best programming language), using pest, to be as similar to Rust as possible, but compiling to Java.

I second pest.rs. Using it is fairly intuitive and there's also a live playground on their website which is great for quickly developing and testing your AST (abstract syntax tree) parser for whatever language you're implementing.

This is where you'll run into trouble. People who write parsing-related Rust crates generally write things like pest that expect their syntax to be defined completely at compile time so the parser can be run through the compiler's optimizers for best performance.

Give https://pest.rs a try.

For now I have used pest to generate an AST that borrows from the given input. But if I can manage to make the parser generic over the return type it may be worth a refactoring.