Re: [Pharo-users] GSoC Proposal - Improve Code Completion

Hi Stef, 2017-04-02 8:24 GMT-03:00 Stephane Ducasse : > Super. > Did you read the previous discussions and suggestions in the past in this > mailing-list? > Yes I did. I put some of the ideas in the proposal. Thanks

[Pharo-users] GSoC Proposal - Improve Code Completion

Hi everyone! I'm trying to apply to GSoC and I have a proposal about Code completion. I would like to share with you: https://docs.google.com/document/d/1R8zAq415UCqtn3AoAcRGDSQFZ_5QgL88nQu6R7gozVE/edit?usp=sharing I know you guys have a lot of ideas around code completion, so any kind of feedba

Re: [Pharo-users] Feedback on #assert: vs. #assert:equals:

> on it! > > Thanks, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Oct 21, 2015, at 10:21 PM, Nahuel Garbezza wrote: > > Hi everyone, > > I'

[Pharo-users] Feedback on #assert: vs. #assert:equals:

Hi everyone, I'm using Pharo for teaching and we use TDD since the beginning. I've noticed that if you use #assert: on a test, like this: self assert: object messageReturningBoolean It gives you strange results in terms of feedback if the result is not a boolean. I would expect an AssertionFaile