> On 31 Aug 2017, at 19:07, Stephane Ducasse <[email protected]> wrote:
>
> On Wed, Aug 30, 2017 at 9:50 PM, Tim Mackinnon <[email protected]> wrote:
>> I’m looking for some feedback on the usage of
>> RBParser>>#parseMethod:onError:.
>>
>> I am looking at ways of improving the way we edit code - and making things
>> work (as least for me - but maybe for everyone) a bit more like IntelliJ
>> where they have some great code operations and very good keyboard support.
>> We are certainly close, but at times feel a bit clumsy - which is a shame as
>> we have far better infrastructure to support equivalent features. So I
>> thought I would have a go.
>
> Excellent!!!
>
>
>> Anyway - step one (which I think I’ve come close on), was to teach
>> senders/implementors to look at the AST so you don’t have to highlight
>> exactly what you want to search on - instead it can infer from your cursor…
>> however my next step was to improve how we can select code to ease
>> refactoring, bracketing etc…
>
> Yes but we have to handle broken code then.
> Did you check how smart suggestions did it for code that compiled?
>
I looked some weeks ago and made some notes what to do… but I fear this has to
wait for next week,
there is no way that I can do anything till ESUG…
Marcus
