You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A common instance of DemandBuilder is used for handling all offer proposals for a demand. Yet we modify it in _handle_proposal() when negotiating a single proposal. That may be a bug.
maybe we should act on @zakaprov's idea of only passing the properties/constraints to the handler so that we're sure they cannot be modified ... - or - maybe we should just construct a Demand object and pass that ? ... or use our "own" Demand dataclass / namedtuple that already has those properties/constraints frozen?
The text was updated successfully, but these errors were encountered:
A common instance of
DemandBuilder
is used for handling all offer proposals for a demand. Yet we modify it in_handle_proposal()
when negotiating a single proposal. That may be a bug.maybe we should act on @zakaprov's idea of only passing the properties/constraints to the handler so that we're sure they cannot be modified ... - or - maybe we should just construct a Demand object and pass that ? ... or use our "own" Demand dataclass / namedtuple that already has those properties/constraints frozen?
The text was updated successfully, but these errors were encountered: