a().c().d().a(); Super{}.a().d().e(); // phew... getting really complicatedWITH P0847, IT'S SIMPLER All the same flat pattern. struct Builder { template Self& a(this Self&& deduplication/correctness-by-compiler Completeness-by-compiler Class interface gets "simpler & safer on the outside" Constrained descendants Simpler member function pointersADT STYLE ADVANTAGES Code deduplication/co deduplication/correctness-by-compiler Completeness-by-compiler Class interface gets "simpler & safer on the outside" Constrained descendants Simpler member function pointers Easier patternsADT STYLE ADVANTAGES Code

new language” again, for the whole language?5 Major improvement via directed evolution 10 simpler metric: 90% of today’s guidance not needed 50 safer metric: 98% fewer type/bounds/init/lifetime metafunction on an ordinary type Compile-time library, not baked-in → a more powerful language can be simpler Metafunction can: apply defaults, enforce requirements, and generate code Same safeties as enum metafunction on an ordinary type Compile-time library, not baked-in → a more powerful language can be simpler Metafunction can: apply defaults, enforce requirements, and generate code Same safeties as enum

77 Concurrent Queues Bounded? Yes – simpler & faster Blocking? # Consumers? Message Size? Dispatch? Type Support?78 Concurrent Queues Bounded? Yes – simpler & faster Blocking? No – readers don’t Bounded? Yes – simpler & faster Blocking? No – readers don’t affect the writer # Consumers? Many Message Size? Dispatch? Type Support?80 Concurrent Queues Bounded? Yes – simpler & faster Blocking Message Size? Variable length Dispatch? Type Support?81 Concurrent Queues Bounded? Yes – simpler & faster Blocking? No – readers don’t affect the writer # Consumers? Many Message Size? Variable

pre-existing beans which provide only multi-argument constructors, and no setters. Additionally, for simpler beans, some people prefer the constructor approach as a means of ensuring beans can not be constructed although an around advice can accomplish the same thing. Using the most specific advice type provides a simpler programming model with less potential for errors. For example, you don't need to invoke the proceed() and the AOP Alliance does not currently define pointcut interfaces. 5.3.2.2. Before advice A simpler advice type is a before advice. This does not need a MethodInvocation object, since it will only

pre-existing beans which provide only multi-argument constructors, and no setters. Additionally, for simpler beans, some people prefer the constructor approach as a means of ensuring beans cannot be constructed although an around advice can accomplish the same thing. Using the most specific advice type provides a simpler programming model with less potential for errors. For example, you don't need to invoke the proceed() and the AOP Alliance does not currently define pointcut interfaces. 5.3.2.2. Before advice A simpler advice type is a before advice. This does not need a MethodInvocation object, since it will only

pre-existing beans which provide only multi-argument constructors, and no setters. Additionally, for simpler beans, some people prefer the constructor approach as a means of ensuring beans cannot be constructed although an around advice can accomplish the same thing. Using the most specific advice type provides a simpler programming model with less potential for errors. For example, you don't need to invoke the proceed() and the AOP Alliance does not currently define pointcut interfaces. 5.3.2.2. Before advice A simpler advice type is a before advice. This does not need a MethodInvocation object, since it will only

pre-existing beans which provide only multi-argument constructors, and no setters. Additionally, for simpler beans, some people prefer the constructor approach as a means of ensuring beans cannot be constructed although an around advice can accomplish the same thing. Using the most specific advice type provides a simpler programming model with less potential for errors. For example, you don't need to invoke the proceed() and the AOP Alliance does not currently define pointcut interfaces. 5.3.2.2. Before advice A simpler advice type is a before advice. This does not need a MethodInvocation object, since it will only

pre-existing beans which provide only multi-argument constructors, and no setters. Additionally, for simpler beans, some people prefer the constructor approach as a means of ensuring beans cannot be constructed although an around advice can accomplish the same thing. Using the most specific advice type provides a simpler programming model with less potential for errors. For example, you don't need to invoke the proceed() and the AOP Alliance does not currently define pointcut interfaces. 5.3.2.2. Before advice A simpler advice type is a before advice. This does not need a MethodInvocation object, since it will only

pre-existing beans which provide only multi-argument constructors, and no setters. Additionally, for simpler beans, some people prefer the constructor approach as a means of ensuring beans cannot be constructed although an around advice can accomplish the same thing. Using the most specific advice type provides a simpler programming model with less potential for errors. For example, you don't need to invoke the proceed() and the AOP Alliance does not currently define pointcut interfaces. 5.3.2.2. Before advice A simpler advice type is a before advice. This does not need a MethodInvocation object, since it will only