Alessandro Coglio
Alessandro Coglio
If I understand correctly, currently the Leo compiler requires array indices to be `u32`: am I correct? But the documentation (https://developer.aleo.org/developer/language/arrays_and_tuples#array-indexing) says `u8/u16/u32`, so we need to resolve that discrepancy...
Thanks for the clarification. I think that the main point I was making is that a Hindley-Milner type inference algorithm would eliminate the current asymmetry between `1-u16` and `1u16-1`, and...
@Orphon I would make it an option in the fuzzer, in case we relax the restriction later, or in case there are objections against restricting array indices to `u32` for...
After further conversion on Discord, it looks like the problem may go away after doing a `leo clean`. I've seen this issue as well. Still, arguably it shouldn't necessary to...
Yes, great use case for error recovery.
Natively implemented functions with no bodies were proposed here: https://github.com/AleoHQ/leo/blob/master/docs/rfc/010-native-functions.md#proposal.
Sounds good to me. @damirka Would you like to do that?
Initial discussion on the topic is at #479.
In Leo we still need to check that a function body always returns (an expression of the appropriate type), it's not enough to check that all `return`s have expressions of...
This relates to #1847.