Throw a runtime error for registrations that occur after startup
This specifically comes up for templated entry methods that aren't explicitly instantiated in the ci file. If you forgot to instantiate a version of the templated entry method, the code still compiles and links fine but at runtime, the behavior is undefined and no errors are ever thrown. One quick fix for this behavior would be to at least throw an error if a new registration occurs after startup.
#5 Updated by Eric Mikida 9 months ago
I think that's just a symptom of the example program I gave you. The call to the entry method that wasn't instantiated was done in the main chare constructor, so it was still during startup. If you move that call to somewhere after startup completes then I suspect multicore will have the same problem.