Very cool. I'm always on the lookout for languages - especially beginner-friendly ones - that are good candidates for building Wasm Components (my use case is a fantasy console with Wasm game cartridges). Have you given any thought to supporting Wasm Components as a build target?
Doolang i started for writing server and apis easily and simply, but you points make sense for Wasm components. Not planned as of now as this is just starting point, but surely would take you thought for my further roadmap. Honestly i'm not too much expert in such thing yet, but would appreciate if you have any other more recommendations and suggestions
Algebraic data types please. When you programme in Haskell, you use them all time, and yet support is missing in so many languages. It's one of the things that makes Swift look attractive to me.
Hi, thanks for pointing this out. Yeah struct and enum are alredy in pipeline. memroy mgmt and codegen work pending for those 2. Planning to release in 0.3.0 but let me see if possible on next release of 0.2.0
Struct enums are base of any type safe language will surely add in upcoming releases.
Hi, Yeah make sense, but I don't have any buzzing goal right now, doolang is not any dsl, just to ensure high level syntax for developer writing backend servers apis. And not started as learning project. Will move forward as per feedback of community and requirement but not such specific target im aiming. so again simple concept is keep it simple to write with speed and security
I understand your intensions, but for compiled languages usually it takes years to be accepted by developers as a mature language. It is so even for Go and Rust. Both of them has giants behind them and, again, it took many years for them. As a solo developer you could make it more specific to become popular in some particular field and then to scale it. If the learning is too simple for you, then you can choose anyth…
True, it takes years. And as a solo dev its really hard. Turning into product really makes sense, i understood now i need something unique or specific feature. but as of now only writing apis routers and server with super simple syntax with speed and security only having in my mind. but I value your point, do you have any suggestions or recommendations? I'm also thinking to start new post to take ideas and suggestion from community.
> Doo provides a rich set of built-in types:
>
> Type Description Example
> Int 32-bit signed integer 42, -10
> Str UTF-8 string "Hello, World!"
> Bool Boolean value true, false
32-bit signed integer is the only numeric type in that "rich" set?!?
> Doo provides a rich set of built-in types: > > Type Description Example > Int 32-bit signed integer 42, -10 > Str UTF-8 string "Hello, World!" > Bool Boolean value true, false 32-bit signed integer is the only numeric type in that "rich" set?!?
Good point, will remove that word, btw will added unsigned float in upcoming release. Thanks for that comment.
Nooooo! "valgrind memory leak". Aaargh. Valgrind (memcheck) is not just a leak detection tool. Leak detection is so unimportant that it isn't even turned on by default.
Thanks for pointing that out. I didn’t actually know all the details about how Valgrind works under the hood just that it does memory checking. I'll definitely read up more on it. If you have any good resources or tips, I'd appreciate your suggestions!
Thanks for pointing that out. I didn’t actually know all the details about how Valgrind works under the hood just that it does memory checking. I'll definitely read up more on it. If you have any good resources or tips, I'd appreciate your suggestions!
I wrote a series of articles for ACCU overload back around 2012 to 2013. This was in 6 parts. Introduction https://accu.org/journals/overload/20/108/floyd_1930/ Basic memcheck https://accu.org/journals/overload/20/109/floyd_1913/ Advanced memcheck https://accu.org/journals/overload/20/110/floyd_1905/ Cachegrind and Callgrind https://accu.org/journals/overload/20/111/floyd_1886/ Massif https://accu.org/journals/overlo…
THanks for sharing, will take a look surely, as memroy mgmt will be crucial for doolang. And I can see you are valgrind developer?
I wrote a series of articles for ACCU overload back around 2012 to 2013. This was in 6 parts. Introduction https://accu.org/journals/overload/20/108/floyd_1930/ Basic memcheck https://accu.org/journals/overload/20/109/floyd_1913/ Advanced memcheck https://accu.org/journals/overload/20/110/floyd_1905/ Cachegrind and Callgrind https://accu.org/journals/overload/20/111/floyd_1886/ Massif https://accu.org/journals/overlo…
THanks for sharing, will take a look surely, as memroy mgmt will be crucial for doolang. And I can see you are valgrind developer?