Baggage::Set docu differs from implementation

[Reneg973]

What is the expected behavior?
See docu Baggage
What is the actual behavior?
Baggage::Set is currently behaving like a const function returning a new object, not modifying the old one.

As Delete() also creates a new object it would be best to just adapt the docs, right?

[marcalff]

What is the expected behavior? See docu Baggage

Key points from the api documentation:

The Baggage container MUST be immutable, so that the containing Context also remains immutable.

Set Value: Returns a new Baggage that contains the new value.

What is the actual behavior? Baggage::Set is currently behaving like a const function returning a new object, not modifying the old one.

As Delete() also creates a new object it would be best to just adapt the docs, right?

Baggage is implemented as expected, the actual behavior is indeed correct.

[Reneg973]

What is the expected behavior? See docu Baggage

Key points from the api documentation:

The Baggage container MUST be immutable, so that the containing Context also remains immutable.

Set Value: Returns a new Baggage that contains the new value.

What is the actual behavior? Baggage::Set is currently behaving like a const function returning a new object, not modifying the old one.
As Delete() also creates a new object it would be best to just adapt the docs, right?

Baggage is implemented as expected, the actual behavior is indeed correct.

The part with the immutability is correct, but the example is wrong, see:

baggage.Set('a', 'B% 💼');
baggage.Set('A', 'c');
baggage.Get('a'); // returns "B% 💼"
baggage.Get('A'); // returns "c"

It should be something like:

auto baggage2 = baggage.Set('a', 'B% 💼');
auto baggage3 = baggage2.Set('A', 'c');
baggage3.Get('a'); // returns "B% 💼"
baggage3.Get('A'); // returns "c"