Github user phrocker commented on a diff in the pull request:

    https://github.com/apache/nifi-minifi-cpp/pull/432#discussion_r232751327
  
    --- Diff: nanofi/src/api/nanofi.cpp ---
    @@ -323,55 +360,45 @@ int transmit_flowfile(flow_file_record *ff, 
nifi_instance *instance) {
     
     flow * create_new_flow(nifi_instance * instance) {
       auto minifi_instance_ref = 
static_cast<minifi::Instance*>(instance->instance_ptr);
    -  flow *new_flow = (flow*) malloc(sizeof(flow));
    -
    -  auto execution_plan = new 
ExecutionPlan(minifi_instance_ref->getContentRepository(), 
minifi_instance_ref->getNoOpRepository(), 
minifi_instance_ref->getNoOpRepository());
    -
    -  new_flow->plan = execution_plan;
    -
    -  return new_flow;
    +  return new flow(minifi_instance_ref->getContentRepository(), 
minifi_instance_ref->getNoOpRepository(), 
minifi_instance_ref->getNoOpRepository());
     }
     
     flow *create_flow(nifi_instance *instance, const char *first_processor) {
       if (nullptr == instance || nullptr == instance->instance_ptr) {
         return nullptr;
       }
       auto minifi_instance_ref = 
static_cast<minifi::Instance*>(instance->instance_ptr);
    -  flow *new_flow = (flow*) malloc(sizeof(flow));
    -
    -  auto execution_plan = new 
ExecutionPlan(minifi_instance_ref->getContentRepository(), 
minifi_instance_ref->getNoOpRepository(), 
minifi_instance_ref->getNoOpRepository());
     
    -  new_flow->plan = execution_plan;
    +  flow *new_flow = new flow(minifi_instance_ref->getContentRepository(), 
minifi_instance_ref->getNoOpRepository(), 
minifi_instance_ref->getNoOpRepository());
     
       if (first_processor != nullptr && strlen(first_processor) > 0) {
         // automatically adds it with success
    -    execution_plan->addProcessor(first_processor, first_processor);
    --- End diff --
    
    What are you basing the statement, "it's now faster than it was?" What 
profiler did you use to gather this, and what benefit does that have over 
readability concerns?


---

Reply via email to