gluax

@acoglio We do accept either `1-u16` or `1u16-1` in implicit situations. The problem is that array indexes are not implicit. By default, we accept them to be u32. The fix...

@acoglio we do accept all those types already in indexing, though I think it would be better if we only did u32. `x[1u16]` works as does `x[1u16 - 1]`. The...

@acoglio and I hopped in a call. We decided once type casting is rolled out, we can limit the index type to u32, for loops and indexing.

@0rphon, yea that might be a good idea so we can spot any issues with that sooner rather than later.

`let b = 4294967295u32 + 1u32;` now prints 0 instead of 1. Everything else still results with the same numbers as before.

The issue is in snarkvm_gadets `addmany` function definition in the `uint_impl` macro implementation for addition. I would assume for other operations that the issue is similar.

@howardwu, do you mean having some library agnostic frontend that lets someone build a GUI from Leo? Something like QT?

The point is to not know zero-knowledge hence this rename makes sense.

@acoglio ah oop yea forgot about that. We can turn this feature into the feature representing that RFC since we usually have a feature/epic representing an RFC. The main change...

@damirka probably could/should be.