title: Performance difference of separate DataWeave update function calls vs. nested update function calls
body: <p>What is the performance difference between these two DataWeave expressions?</p>
  <p>In this example there are three update operators. The destination branch case statement interferes with the child .*flight.destination.longitude and .*flight.destination.latitude case statements.</p>
  <p>First is three separate update operators chained together using infix notation:</p>
  <pre><code>reservationsXml 
  update {
      case flight at .reservations.*reservation.*flight -&gt; flight - &quot;flightCode&quot;  
  }
  update {
      . . . 
      //case dest at .reservations.*reservation.*flight.*destination -&gt; dest
  }
  update {
      case long at .reservations.*reservation.*flight.destination.longitude -&gt; 
          long as Number as String {format: &quot;###.000&quot;} 
      case lat at .reservations.*reservation.*flight.*destination.latitude -&gt;        
          lat as Number as String {format: &quot;###.000&quot;} 
  }
  update {
      case dest at .reservations.*reservation.*flight.*destination -&gt; dest - &quot;ICAO&quot;
  }
  </code></pre>
  <p>vs. putting the second and third update operators inside the previous case statement.</p>
  <pre><code>update {
      case flight at .reservations.*reservation.*flight -&gt; ( flight - &quot;flightCode&quot; )  
      update {
          case dest at .*destination -&gt; 
              (dest - &quot;ICAO&quot;)
              update {
                  case long at .longitude -&gt; 
                      long as Number as String {format: &quot;###.000&quot;} 
                  case lat at .latitude -&gt; 
                      lat as Number as String {format: &quot;###.000&quot;} 
              }
      }
  }
  </code></pre>