Alex Hansen

Hm, I think a lot of the above can remain scoped. Address, ContractId, and Identity, Vec, assert, require, and revert should probably be included. But `msg_sender`, `transfer`, `msg_amount`, `msg_asset_id`, and...

That's a good question. This is really subjective. Personally, I dislike magical global functions in general, although data structures are less offensive to me. That's purely subjective though, so let's...

I think the RFC will resolve this. The program type at the top of the file is certainly a sort of concession as we originally had no better way to...

Yeah, so our error renderer in `forc` currently can only render one span per error/warning. In Rust, sometimes there are errors that show multiple spans, like, "this value was moved...

related: #346

Originally, I designed this with the trait/type paradigm in mind, for consistency. An ABI is like a trait, and a contract is like a type. This forms a metaphor where...

That make sense, We did originally have program types as wrappers with braces around the entire file, but found that the extra level of indentation it introduced to everything was...

One thing I am curious about is the portability of these intrinsics. Given that the EVM's word size is different, the quad word intrinsic would have to load `256 *...

> Aren't we going to have different intrinsics for different targets? Hmm, my mental model has been that we will use the same intrinsics and accomplish portability by implementing the...

We also need to standardize how we define what intrinsics are allowable for what backends, and it should be thoroughly considered.. > We could actually have just one 'intrinsic' which...