Changeset f8c1222 in Lumiera

Timestamp:

2026-09-04T23:29:51Z (5 weeks ago)

Author:

Ichthyostega <prg@…>

Branches:

dev/play

Children:

a4ae568

Parents:

41adaa18

git-author:

Ichthyostega <prg@…> (04/09/26 21:41:42)

git-committer:

Ichthyostega <prg@…> (04/09/26 23:29:51)

Message:

Parameters: work out a solution for an optimised code-path

Overall, this is a questionable endeavour...

• I want a framework that can be extended flexibly
• I am concerned about the performance penalty of that flexibility

What makes this situation problematic is the fact that I am deep in
prototyping work here, and have not the slightest idea as to what would be
the actual usage context. So I am lacking a point of reference, yet still
I am engaged into a very tricky (premature) optimisation...

Anyway. I have now found a way to integrate an optimised access code-path
in a safe way, while retaining the general case with flexible type conversion:

• whenever a BaseDomain<X> is used, a corresponding type-ID is marked into the ID-Record
• this allows when it is possible to side-step any type conversion,
• in which case we can also forcibly side-step the virtual dispatch, and invoke directly the value-accessors of the default implementation, reaching into the embedded value buffer.

(No files)