Project

General

Profile

Bug #1227

Feature #1224: Automate simple uses of TRAM small-message aggregation

Support template entry methods in generated code from TRAM [aggregate] entry method attribute

Added by Phil Miller almost 3 years ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
09/28/2016
Due date:
% Done:

0%


Related issues

Related to Charm++ - Bug #1946: Charmxi segfaults with aggregate keyword on explicit declarations of templated client Merged 07/15/2018

History

#1 Updated by Eric Bohm almost 3 years ago

  • Assignee set to Eric Mikida

#2 Updated by Eric Mikida about 2 years ago

  • Target version changed from 6.8.0 to 6.8.1
  • Tags set to templates, TRAM, charmxi

Being deferred to 6.8.1. The current workaround is to use overloaded entry methods for each type, instead of a templated entry method, and have each of them just delegate to a regular templated method. This hurts modularity a bit, but for cases where all types that will be passed to the entry method are known up front this should be a sufficient workaround for the time being.

#3 Updated by Eric Bohm almost 2 years ago

  • Target version changed from 6.8.1 to 6.9.0

#4 Updated by Eric Mikida over 1 year ago

  • Target version changed from 6.9.0 to Unscheduled

Deferring. The current workaround still exists, this feature is not heavily used, and would require a decent amount of change to code-gen.

#5 Updated by Evan Ramos about 1 year ago

  • Related to Bug #1946: Charmxi segfaults with aggregate keyword on explicit declarations of templated client added

Also available in: Atom PDF