The Hare programming language

Post by ddevault » Mon, Apr 25, 2022, 5:39 PM UTC

thrtythreeforty wrote: post #183

ddevault wrote: post #28

Earlier quoted context omitted.

> Not supporting Windows and macOS will likely hurt the adoption of the language. Not among our target audience it won't. > Anyway, is it possible to target bare-metal with Hare? Is it possible to use it without the standard library? Yes. Here are two kernels written in Hare that don't use the stdlib: https://git.sr.ht/~sircmpwn/helios https://git.sr.ht/~yerinalexey/carrot

I hope you'll reconsider this in the long term, not because I think Windows/macOS are great (my feelings for them range between "ugh" and abject horror depending on the day). Rather, I think it would be good because it makes a language much more palatable for mainstream adoption if it's possible for programs written to be ported to Windows/macOS. Languages need the positive adoption feedback loop. Rust would not be a…

Post by woodruffw » Mon, Apr 25, 2022, 5:45 PM UTC

IshKebab wrote: post #193

zozbot234 wrote: post #45

Earlier quoted context omitted.

> C++ definitely isn't it, and while Rust does bring significant advances in this field, it's a very large and complicated language. It really isn't. Not compared to C++, at least. Or to managed language runtimes, which are just as "large and complicated", only beneath the hood.

Rust is definitely as complicated as C++. However its complexity isn't as big of a deal because it's so much safer. If you forget one of the extremely complicated Rust rules you'll get a compile error. If you forget one of the extremely complicated C++ rules you hopefully will get a compile error. Maybe a warning with `-Wall` or maybe you'll silently get memory errors at runtime!

Post by xigoi » Mon, Apr 25, 2022, 5:54 PM UTC

torresjrjr wrote: post #228

xigoi wrote: post #207

Earlier quoted context omitted.

But why not use a single character? With the double colon, something like foo::bar(xyz) looks like bar is “closer” to xyz, when in fact it's closer to foo.

A single ':' is used for other things, like casting types. let x: int = 0; It's so that the compiler can distinguish between those two, and likely some other areas too.

Post by metaltyphoon » Mon, Apr 25, 2022, 6:05 PM UTC

frou_dh wrote: post #217

metaltyphoon wrote: post #187

Earlier quoted context omitted.

> To distinguish between an instance and a namespace? I’m with OP here. C# proves that . reduces the noise substantially.

Only somewhat related, but when reading docs/comments that mention some method `class.method`, it's annoying when that's ambiguous and could mean either a static method or an instance method. In the Ruby world, I think they have the convention of writing `class#method` in docs/comments when mentioning an instance method, and `class.method` when mentioning a static method.

Post by zozbot234 » Mon, Apr 25, 2022, 6:09 PM UTC

mamcx wrote: post #195

vladharbuz wrote: post #21

Earlier quoted context omitted.

I can sort of understand where you're coming from — manual memory management can be difficult, and doing it improperly can cause bugs. However, in my experience, we're very far from having a magical solution for memory management. C++ definitely isn't it, and while Rust does bring significant advances in this field, it's a very large and complicated language. Unfortunately, the memory management strategy of every oth…

> while Rust does bring significant advances in this field, it's a very large and complicated language. The gist of Rust on this fairly easy, is the heritage/chasing of C++ that makes Rust complicated. A "Rust simple like pascal/c" have potential and I bet 1 billon the borrow checker will not make it hard to use (check https://vale.dev )