C++: string_view: Deep dive Jasmine Lopez Prithvi Okade 1Topics • Motivation • Performance benefits & basics • string_view: Constructors, useful functions • string vs. string_view and their interoperability '\n'; } hello hello hello Apart from this convenience, string_view also provides performance benefits which we will see shortly.Basics • string_view does not allocate any memory. • It consists of sv{pchar + 1, 2}; puts(sv.data()); ello Don’t do this when you are using string_view 6Performance benefits • The fact that string_view does not allocate memory can be used to gain performance in some

GIVES PERF BENEFITS JIT GIVES PERF BENEFITS 3 . 3WHY JIT-COMPILE? WHY JIT-COMPILE? AOT IS NOT POSSIBLE AOT IS NOT POSSIBLE AOT IS NOT DESIRABLE AOT IS NOT DESIRABLE JIT GIVES PERF BENEFITS JIT GIVES GIVES PERF BENEFITS JIT GIVES PRODUCTIVITY BENEFITS JIT GIVES PRODUCTIVITY BENEFITS 3 . 3WHY JIT-COMPILE? WHY JIT-COMPILE? AOT IS NOT POSSIBLE AOT IS NOT POSSIBLE AOT IS NOT DESIRABLE AOT IS NOT DESIRABLE DESIRABLE JIT GIVES PERF BENEFITS JIT GIVES PERF BENEFITS JIT GIVES PRODUCTIVITY BENEFITS JIT GIVES PRODUCTIVITY BENEFITS JIT ALLOWS DIFFERENT WORKFLOWS/USE CASES JIT ALLOWS DIFFERENT WORKFLOWS/USE CASES

Unrelated (no relation exists) We use orthogonality to: 1. Remove interactions 2. Reduce coupling Benefits: • Less complexity • Fewer edge cases • Increased stability • Greater reuse • Better scaling Producer ➔ Consumer: Work items are arbitrarily produced; and each is consumed exactly once • Benefits: Creating work is obviously correlated with understanding for how work is completed (consumed) Producer ➔ Consumer: Work items are arbitrarily produced; and each is consumed exactly once • Benefits: Creating work is obviously correlated with understanding for how work is completed (consumed)

of the container or how it is accessed, and remains uncoupled from other code, with all ensuing benefits. EJBs may also use this stub/proxy approach to delegate to a plain java implementation object, coming method. This method will create an AOP proxy wrapping a target object. One of the most important benefits of using a ProxyFactoryBean or other IoC-aware class to create AOP proxies, is that it means that be done in cooperation with the AspectJ community. We believe that this will provide significant benefits for both Spring and AspectJ users, in the following areas: • Allowing AspectJ aspects to be configured

of the container or how it is accessed, and remains uncoupled from other code, with all ensuing benefits. EJBs may also use this stub/proxy approach to delegate to a plain java implementation object, coming method. This method will create an AOP proxy wrapping a target object. One of the most important benefits of using a ProxyFactoryBean or other IoC-aware class to create AOP proxies, is that it means that be done in cooperation with the AspectJ community. We believe that this will provide significant benefits for both Spring and AspectJ users, in the following areas: • Allowing AspectJ aspects to be configured

of the container or how it is accessed, and remains uncoupled from other code, with all ensuing benefits. EJBs may also use this stub/proxy approach to delegate to a plain java implementation object, coming method. This method will create an AOP proxy wrapping a target object. One of the most important benefits of using a ProxyFactoryBean or other IoC-aware class to create AOP proxies, is that it means that be done in cooperation with the AspectJ community. We believe that this will provide significant benefits for both Spring and AspectJ users, in the following areas: • Allowing AspectJ aspects to be configured

configuration”Significant benefits:Significant benefits: ⊡ No need for special hardwareSignificant benefits: ⊡ No need for special hardware ⊡ Short development timeSignificant benefits: ⊡ No need for special Short development time ⊡ Easy access to simulator mode without additional buildingSignificant benefits: ⊡ No need for special hardware ⊡ Short development time ⊡ Easy access to simulator mode without

of the container or how it is accessed, and remains uncoupled from other code, with all ensuing benefits. EJBs may also use this stub/proxy approach to delegate to a plain java implementation object, coming method. This method will create an AOP proxy wrapping a target object. One of the most important benefits of using a ProxyFactoryBean or other IoC-aware class to create AOP proxies, is that it means that be done in cooperation with the AspectJ community. We believe that this will provide significant benefits for both Spring and AspectJ users, in the following areas: • Allowing AspectJ aspects to be configured

of the container or how it is accessed, and remains uncoupled from other code, with all ensuing benefits. EJBs may also use this stub/proxy approach to delegate to a plain java implementation object, coming method. This method will create an AOP proxy wrapping a target object. One of the most important benefits of using a ProxyFactoryBean or other IoC-aware class to create AOP proxies, is that it means that be done in cooperation with the AspectJ community. We believe that this will provide significant benefits for both Spring and AspectJ users, in the following areas: • Allowing AspectJ aspects to be configured

of the container or how it is accessed, and remains uncoupled from other code, with all ensuing benefits. EJBs may also use this stub/proxy approach to delegate to a plain java implementation object, coming method. This method will create an AOP proxy wrapping a target object. One of the most important benefits of using a ProxyFactoryBean or other IoC-aware class to create AOP proxies, is that it means that be done in cooperation with the AspectJ community. We believe that this will provide significant benefits for both Spring and AspectJ users, in the following areas: • Allowing AspectJ aspects to be configured