Class DeleteIdPoolOutputBuilder
- java.lang.Object
-
- org.opendaylight.yang.gen.v1.urn.opendaylight.genius.idmanager.rev160406.DeleteIdPoolOutputBuilder
-
- All Implemented Interfaces:
org.opendaylight.yangtools.concepts.Builder<DeleteIdPoolOutput>
,org.opendaylight.yangtools.concepts.CheckedBuilder<DeleteIdPoolOutput,java.lang.IllegalArgumentException>
,org.opendaylight.yangtools.concepts.Mutable
,org.opendaylight.yangtools.concepts.MutationBehaviour<org.opendaylight.yangtools.concepts.Mutable>
public class DeleteIdPoolOutputBuilder extends java.lang.Object implements org.opendaylight.yangtools.concepts.Builder<DeleteIdPoolOutput>
Class that buildsDeleteIdPoolOutputBuilder
instances. Overall design of the class is that of a fluent interface, where method chaining is used.In general, this class is supposed to be used like this template:
DeleteIdPoolOutputBuilder createTarget(int fooXyzzy, int barBaz) { return new DeleteIdPoolOutputBuilderBuilder() .setFoo(new FooBuilder().setXyzzy(fooXyzzy).build()) .setBar(new BarBuilder().setBaz(barBaz).build()) .build(); }
This pattern is supported by the immutable nature of DeleteIdPoolOutputBuilder, as instances can be freely passed around without worrying about synchronization issues.
As a side note: method chaining results in:
- very efficient Java bytecode, as the method invocation result, in this case the Builder reference, is
on the stack, so further method invocations just need to fill method arguments for the next method
invocation, which is terminated by
build()
, which is then returned from the method - better understanding by humans, as the scope of mutable state (the builder) is kept to a minimum and is very localized
- better optimization oportunities, as the object scope is minimized in terms of invocation (rather than method) stack, making escape analysis a lot easier. Given enough compiler (JIT/AOT) prowess, the cost of th builder object can be completely eliminated
- See Also:
DeleteIdPoolOutputBuilder
,Builder
-
-
Constructor Summary
Constructors Constructor Description DeleteIdPoolOutputBuilder()
DeleteIdPoolOutputBuilder(DeleteIdPoolOutput base)
-
Method Summary
All Methods Instance Methods Concrete Methods Modifier and Type Method Description DeleteIdPoolOutputBuilder
addAugmentation(java.lang.Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<DeleteIdPoolOutput>> augmentationType, org.opendaylight.yangtools.yang.binding.Augmentation<DeleteIdPoolOutput> augmentationValue)
<E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<DeleteIdPoolOutput>>
E$$augmentation(java.lang.Class<E$$> augmentationType)
DeleteIdPoolOutput
build()
DeleteIdPoolOutputBuilder
removeAugmentation(java.lang.Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<DeleteIdPoolOutput>> augmentationType)
-
-
-
Constructor Detail
-
DeleteIdPoolOutputBuilder
public DeleteIdPoolOutputBuilder()
-
DeleteIdPoolOutputBuilder
public DeleteIdPoolOutputBuilder(DeleteIdPoolOutput base)
-
-
Method Detail
-
augmentation
public <E$$ extends org.opendaylight.yangtools.yang.binding.Augmentation<DeleteIdPoolOutput>> E$$ augmentation(java.lang.Class<E$$> augmentationType)
-
addAugmentation
public DeleteIdPoolOutputBuilder addAugmentation(java.lang.Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<DeleteIdPoolOutput>> augmentationType, org.opendaylight.yangtools.yang.binding.Augmentation<DeleteIdPoolOutput> augmentationValue)
-
removeAugmentation
public DeleteIdPoolOutputBuilder removeAugmentation(java.lang.Class<? extends org.opendaylight.yangtools.yang.binding.Augmentation<DeleteIdPoolOutput>> augmentationType)
-
build
public DeleteIdPoolOutput build()
- Specified by:
build
in interfaceorg.opendaylight.yangtools.concepts.Builder<DeleteIdPoolOutput>
- Specified by:
build
in interfaceorg.opendaylight.yangtools.concepts.CheckedBuilder<DeleteIdPoolOutput,java.lang.IllegalArgumentException>
-
-