Manuscript (Case [Issue]22671) _Inbox - IdentitySet>>asSet returns an IdentitySet instance instead of Set

Federico Mennite edited Case 22671: IdentitySet>>asSet returns an IdentitySet instance instead of Set: Bug in  _Inbox: Not Spam  •  You are subscribed to this case The copy guarantee isn't a big issue, especially if people are generally aware that conversions don't always guarantee a copy. In my opinion the relationship between strings and wide strings isn't the same as between sets and identity sets. In the former case String and WideString are basically providing the same semantically compatible behavior: they are 2 different classes just to provide more efficient internal behavior depending on the elements(characters) they are holding. Sets and identity sets have least one explicit semantic difference: discriminating against equality or identity. So in the latter case if a method named #asSet it simply makes sense to me to expect it to return an instance of Set. Yes, probably it would make more sense for Set and IdentitySet to share a common ancestry instead of having one being the superclass of the other. I have to do some thinking about it. Federico Priority: 5 – Fix If Time Status: Work Needed Assigned to: Everyone Milestone: Pharo7.0 Go to Case No longer need updates? Unsubscribe from this case. Don't want Manuscript notifications anymore? Update your preferences.

A Manuscript case was edited by Federico Mennite. Case ID: 22671 Title: IdentitySet>>asSet returns an IdentitySet instance instead of Set Status: Work Needed Category: Bug Project: _Inbox Area: Not Spam Priority: 5 - Fix If Time Milestone: Pharo7.0: 9/2/2018 (Past) Assigned To: Everyone URL: https://pharo.manuscript.com/f/cases/22671 The copy guarantee isn't a big issue, especially if people are generally aware that conversions don't always guarantee a copy. In my opinion the relationship between strings and wide strings isn't the same as between sets and identity sets. In the former case String and WideString are basically providing the same semantically compatible behavior: they are 2 different classes just to provide more efficient internal behavior depending on the elements(characters) they are holding. Sets and identity sets have least one explicit semantic difference: discriminating against equality or identity. So in the latter case if a method named #asSet it simply makes sense to me to expect it to return an instance of Set. Yes, probably it would make more sense for Set and IdentitySet to share a common ancestry instead of having one being the superclass of the other. I have to do some thinking about it. Federico You are subscribed to this case. If you do not want to receive automatic notifications in the future, unsubscribe (https://pharo.manuscript.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&command=view&ixBug=22671) from this case.
_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker