Dada, an experimental new programming language

Post by dist-epoch » Wed, Mar 06, 2024, 3:47 PM UTC

OtomotO wrote: post #162

sorenjan wrote: post #138

Changing a quote to change "his" to "theirs" seem like a very Rust community thing to do. > Updated to use modern pronouns. https://dada-lang.org/docs/about/

Non-native-speaker take: I don't care, it just reads a bit "weird" as I learned English before and "theirs" was plural... but I am adaptable. As long as the meaning of the quote isn't changed I couldn't care less and it seems very important to some people. What I personally dislike though is the whole "Ask me my pronouns" thing... like "No, I don't care about your gender or sex, as long as I am not interested in a ro…

Post by turnsout » Wed, Mar 06, 2024, 3:48 PM UTC

jokethrowaway wrote: post #51

The main idea is that leases are an easier concept to understand than borrowing and lifetimes? I don't think it will be, it sounds like a concept of similar complexity and it won't make it an "easy language". People are scared of Typescript, so a typed language with an extra ownership concept will sound exactly like rust in terms of difficulty. Not that I get the reputation of Rust being hard, even as a complete novi…

Post by steveklabnik » Wed, Mar 06, 2024, 3:50 PM UTC

luke-stanley wrote: post #43

mtsr wrote: post #22

Earlier quoted context omitted.

Maybe it’s actually a non-leaky abstraction because it makes the async-nature explicit. The alternative is hiding it, but it’s still going to affect your code, making that effectively a leaky abstraction.

Maybe there could be something like a aprint() wrapper, if the authors wanted to make the async nature explicit? Or something else, probably not this for one of the most common things a programmer must do.

Post by ordu » Wed, Mar 06, 2024, 3:51 PM UTC

color_me_not wrote: post #186

nialv7 wrote: post #150

Earlier quoted context omitted.

I think they didn't do a very good job explaining it. Await doesn't just mean "please run this thunk", it means "I am not going to deal with this thunk, can someone come and take over, just give me the result in the end". What this means, concretely, in Rust, is `.await` will return the thunk to the caller, and the caller should resume the async function when the result is ready. Of course the caller can await again…

So, you mean that this thunk is produced by the async function, and the await keyword will run it asynchronously? In other words, print produces a thunk, and print_point also produces a thunk, and when await is used on the later, it is executed asynchronously, which will execute the print also asynchronously. So we end up with 3 different execution context: the main one, a one for each "await"? What is the point of t…

Post by stephen » Wed, Mar 06, 2024, 3:52 PM UTC