Mazdak Farrokhzad
Mazdak Farrokhzad
@bluss Hmm; this seems to me a shorthand for `iter.map(|x| x.and_then(closure))` so idk; it might be a nice ergonomics thing... I think if it makes sense for itertools it makes...
Everything in the list has been stabilized save for `.flatten()` which is getting stabilized atm.
N.B. to make these PR series easier to review, I'd prefer to review the diff just for the changes relevant e.g., to constant folding and not other things.
This seems like a great idea! We could add error recovery for `circuit` => `struct`. Alternative names might be: `data` and `record`, although the latter seems overloaded in Leo specifically,...
I would go for approach 2 under the assumption that the user probably wants to make this live code eventually. This also simplifies the type checker such that we don't...
My take on this is that per approach 2 in https://github.com/AleoHQ/leo/issues/1847#issuecomment-1142077457, this should not fail, i.e. this isn't a bug.
Great idea! We can add error recovery for `function` => `fn`
> We may want to use a different keyword form impl, such as members or methods, which seems more descriptive in the Leo context. By analogy of naming it `struct`...
Another idea for adding methods to a type could be allowing the following in the global scope: ```rust function foo(self: MyType) { ... } ```
Strongly in favor of the separation as well. It solves a bunch of problems and makes things cleaner. > As far as the keyword to introduce those blocks, I still...