I guess not to mix with Tao, next gen OS for Amiga, based on bytecode as distribution format.
Tao: A statically-typed functional language
41–50 of 98 posts
Re: Tao: A statically-typed functional language
#42Earlier quoted context omitted.
> No dependant types either. You're funny
How so? I personally find dependant types to be very interesting, but I get that they are a PITA to implement. So, for me, it was simply an observation that there are currently no plans for dependant types. No value judgement intended.
Not to be pendantic, but I think you made a joke without realizing it.
Re: Tao: A statically-typed functional language
#43I don't understand what the possible use case for using a \ for the final bar for sum types would be. It would just make it a diff to add a new item at the end. I was hoping it had Unicode support looking at the example screenshot, but no, it's just a ligature font confusing users.
Tao isn't indentation-sensitive, so nested `match` expressions are ambiguous without the trailing \ branch. I don't know whether I'll keep this syntax though. I'm increasingly wondering whether it's better to just bite the bullet and go all in with indentation sensitivity. That said, the existing \ syntax can be quite nice to read: https://github.com/zesterer/tao/blob/master/lib/parse.tao#L5...
The \ syntax is my favorite part so far, I’m definitely gonna copy it for my toy language, hope that’s ok ;)
Re: Tao: A statically-typed functional language
#44Earlier quoted context omitted.
Tao isn't indentation-sensitive, so nested `match` expressions are ambiguous without the trailing \ branch. I don't know whether I'll keep this syntax though. I'm increasingly wondering whether it's better to just bite the bullet and go all in with indentation sensitivity. That said, the existing \ syntax can be quite nice to read: https://github.com/zesterer/tao/blob/master/lib/parse.tao#L5...
The \ syntax is my favorite part so far, I’m definitely gonna copy it for my toy language, hope that’s ok ;)
Go for it! IIRC it was suggested by someone else in the #langdev channel on the Rust Community Discord, so I can't claim to own the idea.
Re: Tao: A statically-typed functional language
#45Hey, author here. I definitely didn't expect to see Tao on Hacker News. As is probably obvious, the language is extremely early in its life, and it's not practical to write anything but trivial examples in it yet. Please don't judge!
I remember a golden age of programming reddit and HN in the late 2000s that inspired me learn a bunch of new programming languages, Haskell the biggest influence among them. It seemed like people were always posting their own personal languages, lisps (I remember the hot takes on Arc lol), and such all the time. I have very fond memories of going through Jack Crenshaw's "Let's Build a Compiler" after seeing it posted a bunch of times, then trying to build my own language in a similar vein.
Cheers to you, and I hope you're learning and having fun working on your project!
Re: Tao: A statically-typed functional language
#46Hey, author here. I definitely didn't expect to see Tao on Hacker News. As is probably obvious, the language is extremely early in its life, and it's not practical to write anything but trivial examples in it yet. Please don't judge!
I remember a golden age of programming reddit and HN in the late 2000s that inspired me learn a bunch of new programming languages, Haskell the biggest influence among them. It seemed like people were always posting their own personal languages, lisps (I remember the hot takes on Arc lol), and such all the time. I have very fond memories of going through Jack Crenshaw's "Let's Build a Compiler" after seeing it posted…
Thanks!
Re: Tao: A statically-typed functional language
#47This looks great! I've actually been experimenting with making a functional language too, in rust - so I'm probably gonna read through the code soon! Also, those error messages look really good - I'm totally gonna try ariadne and chumsky out :)
Good luck! Feel free to open a discussion topic or issue if you have any questions!
Since someone brought it up, and since I don’t speak rust… are the error message formats (i.e. the lines and crossings) made by a rust library or did you implement them? They are certainly visually nice.
Re: Tao: A statically-typed functional language
#48Earlier quoted context omitted.
Good luck! Feel free to open a discussion topic or issue if you have any questions!
Since someone brought it up, and since I don’t speak rust… are the error message formats (i.e. the lines and crossings) made by a rust library or did you implement them? They are certainly visually nice.
They are made by a Rust library, but it's a library I wrote for this project (now used by others too): https://github.com/zesterer/ariadne
Re: Tao: A statically-typed functional language
#49A couple of months agow I had never tried functional programming languages. Having learned Rust in the past year (and loving it ) made me want to try out Haskell since I always wondered about functional languages and I likes Rust's strong type system.
I go a bit dissappointed with Haskell, but right now I'm reading Tao's README and this looks like everything I've ever wanted ! I'm gonna try it out right now.
Re: Tao: A statically-typed functional language
#50A couple of months agow I had never tried functional programming languages. Having learned Rust in the past year (and loving it ) made me want to try out Haskell since I always wondered about functional languages and I likes Rust's strong type system. I go a bit dissappointed with Haskell, but right now I'm reading Tao's README and this looks like everything I've ever wanted ! I'm gonna try it out right now.
Can you expand on what disappointed you about Haskell. I’m not looking to convert you or anything, just curious.