Idea: Borrowck Transparent Function Calls

Vorpal:

I have found Rust one of the easiest languages to refactor in ... thus needs a refactor anyway

I kind of expected this response. IMO most time it's self-inflicted wound, you won't need the refactor in begin with if you are not using Rust. This cause serious momentum issue, esp in gamedev. Maybe it's suprising to you, but absolute cleanness and correctness is not always the top priority.

Vorpal:

What I do agree would be useful is partial borrowing. But I suspect you would find an explicit version of it works just fine, especially if it is just depth 0 or 1 as you describe. Then you basically only need to update in one or two places for your experiments. I think we should aim to get explicit partial borrowing first and see how that works out.

Ok, disclaimer first: I'm totally not hating or bashing on t-types or t-lang, they do fantastic works.

But here's the thing, partial borrowing (or we call them view types) absolutely won't come out in 3 years, it has much higher language semantic implications. TFC is a much smaller proposal, I can implement it myself in like 2 months. "Wait for view types" is basically equivalent to "forget about this" to me.

Vorpal:

Would it stay that way?

This is one thing I have high confidence with an answer of yes.