Jason Carr

At this point, I'm convinced that :two: might be untenable because private types need to be exposed in disjointness constraints due to the potential to escape into interfaces. Imagine `(_Private...

Sorry, yes it's possible, but it does mean that all of the uses of private types have to appear in disjointness constraints, or the disjointness constraints need to have a...

Thanks for the responses @rowland66. I didn't think to catch that the private methods' safety conditions were being checked by the calling public methods. And I totally get you on...

Oh, if we support resizing up to the length of the buffer, then that is reasonable to be named resize. The only pitfall with that is we may need to...

Most probable explanation: this was latent until the change to allow returning `box` for `trn` recovery. TK_THISTYPE likely gets instantiated as `box` and then the `trn` receiver sees the result...

We discussed this a bit. Refcaps will also need to match all, One edge case / compilcation could be when one of the methods is tag, and another is box/ref,...

This is touched upon but not exactly covered in #449 as it doesn't go into much detail about function receivers, and probably could use a bit more work around what...

@rhagenson I'd have to think about where this could fit. In effect I'd expect this needs to be in a section that describes receiver capabilities or "formally" describes what is...

I believe I was referring to independence from my changes. But in some sense they're nearly independent from each other as well.

Would you think we should have the VCS pick the default name at runtime (asynchronously)? Since it can be either main or master for git a there's a git incantation...