Fixing the Piping/Chaining Issue

[uniment]

@Sukera

that the core problem can be solved without new syntax (as you’ve shown, by implementing a rudimentary autocomplete yourself).

My point was that the actual core problem was one of motivation: people need a reason to work on an autocomplete, hopefully beyond just being an academic pursuit. Which syntax sugar provides. In the same way, somebody was motivated to write an autocomplete for . but not getproperty, despite the former being just sugar for the latter, in the confidence that the autocomplete on . would find heavy use and the effort would not go to waste.

@Sukera

That is a requirement that hasn’t changed, as your code literally has typeof(obj) in it, which is not necessarily something an editor can do because the editor would potentially have to run your code to figure that out, which you surely don’t want (or run type inference on all of your code, which runs into the problem of “partial inference is not implemented”).

With sufficient motivation, somebody smarter than me will figure this out I’m sure. In the meantime, I’d be pretty happy to have autocomplete in REPL mode.