fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

10K
active users

Jan <3

Okay, adding Automatic Reference Counting (ARC), which is thread safe, to what my dream should have. Compared to Swift, their preferred implementation, ORC, doesn’t leak memory when dealing with reference cycles. Although I don’t know if their implementation it thread safe, as well.

Maybe my theoretical should warn, but leak upon reference cycles. It seems to make the implementation easier.

Maybe the compiler can detect if a variable is shared between threads and use atomic operations by default. If not, it’s just like where it is up to the programmer

@rollbrettklauen It's one of the most interesting benefits of the memory model and ownership rules. The compiler can ensure at compile time lots of interesting properties for mutexes, like "one writer, many readers" rule. I think there is a good potential for having some limited Rust-like ownership even in a language with a different memory model.

@orsinium yeah Rust‘s ownership model is definitely interesting, but makes programming in Rust really difficult as well. Whereas Swift is beginner friendly and ensures thread safety as well. I want software written my language to be editable by a junior software dev

@rollbrettklauen @orsinium

Very true! Performance is important but you have to balance how important it is for your use case.

Sometimes all you need is a fast enough language that can be easily adopted by your team.