<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
Hi Eliot,<div><br></div><div>sure, SUnit could put those extensions into Object. I wouldn't want to have those outside SUnit, though. Not sure why. I only consider #assert: a useful tool even outside test cases. Just to document an invariant in a method.</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 09.10.2020 10:24:58 schrieb Eliot Miranda <eliot.miranda@gmail.com>:</p><div style='font-family:Arial,Helvetica,sans-serif'>
<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-size: 14pt">Hi All,</div><div class="gmail_default" style="font-size: 14pt"><br></div><div class="gmail_default" style="font-size: 14pt"><span style="font-family: arial, sans-serif"> moving code from a test into a workspace and back is painful because Object does not implement assert:equals: or assert:equals:description: even though it implements assert:description:. So one has to edit out the equals: moving to the workspace and edit it back in again on the way back. I'd like to suggest implementing Object>>assert:equals: and <span style="color: rgb(0,0,0);font-size: 12pt">Object>>assert:equals:description: but I won't, because someone is bound to criticise it as being too green or ill considered or some other depressing BS.</span></span></div><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><span style="font-size: 10pt;border-collapse: separate"><span style="font-family: arial, sans-serif"><div>_,,,^..^,,,_<br></div><div>best, Eliot</div></span></span></div></div></div></div></div>
</div></blockquote>
</div></body>