#452: [TODO] Don't use MULTI when not needed
---------------------+------------------------------------------------------
Reporter: allison | Owner:
Type: todo | Status: new
Priority: normal | Milestone: 1.4
Component: none | Version:
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
---------------------+------------------------------------------------------
Comment(by chromatic):
I have my doubts about this idea; it makes PMCs more difficult to write
and much more difficult to subclass. In the medium term, making MULTI and
VTABLE calls less expensive will be better overall. (In the long term,
making VTABLE calls multidispatch themselves will actually reduce the
amount of code in the system.)
For now I'd rather see the PMC parser and code generator improved so that
we can add an optimization to collapse "unnecessary" MULTIs into if/else
statements. We can undo that optimization as needed. This would allow us
to keep the source code of PMCs reasonably clear in terms of intended
semantics while taking advantage of short term optimizations and waiting
for longer term optimizations.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/452#comment:1>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
