anamax22

The examples in 1.10.3 are about list's elements. They point out that while list was borrowed, its elements weren't. My question is whether the caller's reference to list is guaranteed...

There seems to be some confusion. I'm not talking about functions that return borrowed references. I'm talking about a case when borrowing doesn't work. Consider the following: ``` # change()...

I'll it say again - I'm not talking about the elements/components of an argument. I'm talking about the argument as a whole, which is the actual borrowed reference. The same...

Minimum: "The caller owns a reference to the object, so the borrowed reference’s lifetime is guaranteed until the function returns. Only when such a borrowed reference must be stored or...

I'm surprised by the assertion that the caller is responsible for knowing when "callee(_GLOBAL)" is safe. If callee is written in python, it is safe. If callee is an extension,...

Please don't rewrite the caller. callee(1.0+35), callee(_GLOBAL), callee(local) should all work. > The caller doesn't need to know anything about callee. It does need to ensure that the reference that...

[1] The caller's implementation is irrelevant because callees should work regardless of the caller. (That's true when the callee is written in python. It should also be true when the...