Re: operation can be dispatching in only one type

["G.B." <bauhaus@futureapps.invalid>]

On 01.12.15 09:46, Dmitry A. Kazakov wrote:
> On Mon, 30 Nov 2015 16:22:12 -0600, Randy Brukardt wrote:
>
> some
> I/O protocol. Countless requests here in c.l.a. concerning instructing the
> compiler to do it right is a proof.
>
> But when it becomes the problem space the compiler knows absolutely nothing
> about handling proxy objects located in the memory. A row of a DB record
> result set is a record for which the compiler has no slightest idea how to
> map it (onto the DB environment, connection, cursor).

Compiler vendors convincing the bosses of the database vending
families to agree on giving up control over I/O and representation,
now that will be quite something! ;-)

> There is no reason why indexing or record member access
> should be less efficient when a user-defined implementation allowed, but
> not actually used.

Sounds a bit like user defined aspects of compilation? What
guarantees would the compiler be able to generate that user
defined mechanics will work at the same level of assurance
as that of "regular" records?