[Azure.Core.Amqp] Lazy Allocation for All Sections

[jsquire]

Summary

The focus of these changes is to enable lazy allocation for all sections of the AmqpAnnotatedMessage type, to align with them being defined as optional by the AMQP specification. In order to allow downstream consumers to test if a section is populated without triggering allocation for the property, the HasSection member has been added.

References and Resources

• API View
• AMQP Specification, section 3.2

[JoshLove-msft]

LGTM. In terms of logistics, we still are planning on GAing the body types in next week or so. I'd rather wait to ship HasSection until we've implemented it in Event Hubs to prove that the API is correct.

[jsquire]

LGTM. In terms of logistics, we still are planning on GAing the body types in next week or so. I'd rather wait to ship HasSection until we've implemented it in Event Hubs to prove that the API is correct.

No objections from me. To be clear, are we comfortable with shipping the body types from a commit or are you asking me to hold off on merging until after that point?

[JoshLove-msft]

LGTM. In terms of logistics, we still are planning on GAing the body types in next week or so. I'd rather wait to ship HasSection until we've implemented it in Event Hubs to prove that the API is correct.

No objections from me. To be clear, are we comfortable with shipping the body types from a commit or are you asking me to hold off on merging until after that point?

I'd prefer to ship from tip of master. I'm not opposed to including this in the GA, but I would prefer to wait until we've done a validation of the API through Event Hubs.

[jsquire]

I'd prefer to ship from tip of master. I'm not opposed to including this in the GA, but I would prefer to wait until we've done a validation of the API through Event Hubs.

I'll leave this open, then, until we ship.

[jsquire]

/check-enforcer evaluate