<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
Hi Patrick.<div><br></div><div>+1 on adding #rehash for Bag ... although it technically depends on #contentsClass ? Hmmm...</div><div><br></div><div>+0.5 on making #rehash non-private. Hmm.... maybe "initialization" would be a fitting category. Well, definitely not "update" or something like that. Clients should normally not call it, right?</div><div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div><blockquote class='history_container' type='cite' style='border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;'>
<p style='color: #AAAAAA; margin-top: 10px;'>Am 05.03.2021 20:12:19 schrieb Rein, Patrick <patrick.rein@hpi.de>:</p><div style='font-family:Arial,Helvetica,sans-serif'>Hi everyone,<br><br>during a recent debugging session I noticed that Bag does not implement #rehash although it is, in essence, a hash-based collection and should therefore probably roughly adhere to the protocol of HashedCollection. Is there a good reason not to have #rehash on Bag?<br><br>On a similar note: HashedCollection>>#rehash is in the `private` protocol but has various senders. As even the class comment mentions the usage of #rehash, I would also propose to move it out of the `private` protocol. :)<br><br>Best wishes,<br>Patrick<br><br></div></blockquote>
</div></body>