josh11b

The most interesting example to me is when interface implementation is involved. So something like: ``` library "i"; interface I {} ``` ``` library "e"; import library "i"; extern class...

Point was to show the issue with extern impl.

> * **No** ability to use this in a class member or struct. How do I call `ref self` methods on class members then? Seems strange since we've been talking...

> > * **No** ability to use this in a class member or struct. > > How do I call `ref self` methods on class members then? Seems strange since...

Just note that we do want the elements of tuples to have their own category, and in general tuples should ideally be able to represent arbitrary argument lists so that...

I'm concerned with cases where we need to use a tuple parameter for the situation where there are multiple variadic arguments. Examples without categories: ``` fn CallTwice[... each T:! type,...

> we _do_ need a way to abstract over / deduce `let` vs. `var` vs. `ref`. I've somewhat omitted that here, but I do think figuring that out is a...

One question we should resolve is whether `ref` should be `nocapture` (and `noalias`) in order to support "move-in-move-out" semantics. Is this an important part of `ref`? The write up doesn't...

My inclination here is to say yes: we have seen a lot of use cases for the adapter feature, and some of those use cases (for example, using adapters to...

Thinking about this again, there is the possibility that we could allow an non-abstract adapter to adapt an abstract class if it doesn't have any abstract methods. Perhaps it would...