pharo

Pharo looks anything but, yet (politely, out of concern and genuine interest) pointing it out gets you hate and verbal violence from the community. I want an open source Smalltalk implementation. I want more people to like Smalltalk. I want more people to use Smalltalk. Pharo could be helpful with these, but it's not. Instead of a gateway into Smalltalk ecosystem, Pharo is an impenetrable wall to new users. And the community doesn't care. There are some people that do care. See Glamorous Toolkit. See Cuis. I wrote a few small pet projects in Pharo, back in 2012. They kept getting broken release after release. And at some point, the default download with official releases stopped working altogether. And never worked again. There's a ticket from 2021 (created years after it stopped working for me) describing the problem: https://github.com/pharo-project/pharo/issues/9729 This is a regression brought about due to another rewrite of something. Still not fixed. You know, I could fix myself and contribute the fix - I have the skills and could potentially find the time. But Pharo and its community burned so many bridges for me that this is not going to happen. Call me petty all you want, but the kinds of people running Pharo are just not worth being helped.

and a copy of the arguments to test with Then, given this collection of MethodFinderSend objects: ^ (self possibleSolutionsForInput: inputCollection) select: [ :send | send resultIn: expectedResult ]. This means: - execute the "resultIn:" method on each of the MethodFinderSend and return a collection of those where this returns true The implementation of this "resultIn:" method is in https://github.com/pharo-project/pharo/blob/c896913a00fa6e2b...: [ [ ^ expectedResult = (receiver perform: selector withArguments: arguments) ] onErrorDo: [ :anError | ^ false ] ] on: Deprecation do: [ :depr | ^ false ] This is, roughly: - try to perform the call - return false if there is an exception - otherwise, return true or false depending on whether the result equals the expected result So yes, it's an exhaustive search over the methods that the receiver's class promises are OK to test. If you write a method that tries to format the hard drive, and your class exports this method in its "selectors to test", then searching for a method on this class will attempt to format your hard drive.