Am I the only one who saw this syntax and immediately though "Man, this looks almost identical to Rust with a few slight variations"?

▲

CupricTea 14 hours ago | parent | next [-]

It seems to just be Rust for people who are allergic to using Rust.

It looks like a fun project, but I'm not sure what this adds to the point where people would actually use it over C or just going to Rust.

▲

nnevatie 14 hours ago | parent | next [-]

> what this adds

I guess the point is what is subtracts, instead - answer being the borrow-checker.

▲

petcat 14 hours ago | parent | next [-]

> answer being the borrow-checker

There is an entire world in Rust where you never have to touch the borrow-checker or lifetimes at all. You can just clone or move everything, or put everything in an Arc (which is what most other languages are doing anyway). It's very easy to not fight the compiler if you don't want to.

Maybe the real fix for Rust (for people that don't want to care), is just a compiler mode where everything is Arc-by-default?

▲

Ygg2 14 hours ago | parent | prev [-]

So it re-adds manual lifetime checking. Got it.

	▲	askyng 6 hours ago \| parent [-]
		It might or might not be a toy project, I'm not sure, but one advantage of subtracting the borrow checking is that the compiler avoids a lot of complex machinery. Borrow checking in Rust isn't sound AFAIK, even after all these years, so some of the problems with designing and implementing lifetimes, region checking, and borrow checking algorithms, aren't trivial.

▲

the__alchemist 14 hours ago | parent | prev [-]

Maybe take the parts of rust the author likes, but still encourages pointers in high level operations?

▲

suioir 14 hours ago | parent | prev | next [-]

I thought the same and felt it looked really out of place to have I8 and F32 instead of i8 and f32 when so much else looks just like Rust. Especially when the rest of the types are all lower case.

▲

unwind 14 hours ago | parent [-]

Agreed, that really stood out as a ... questionable design decision, and felt extremely un-ergonomic which seems to go against the stated goals of the language.

	▲	hyperhello 13 hours ago \| parent [-]
		Every language is apparently required to make one specific version of these totally arbitrary choices, like whether to call the keyword function, func, fun, fn, or def. Once they do, it’s a foolish inconsistency with everything else. What if the language supported every syntax?

▲

turbotim 14 hours ago | parent | prev | next [-]

My immediate thought was it looked a lot like Swift

▲

14 hours ago | parent | prev [-]

[deleted]