Fixing vim's handling of the enclosing-type cache - #771
Conversation
|
Anything blocking this? |
Yes, the lack of people available for reviewing :p So, I just had a look, and it took me a while to see what the actual change was, that's because the diff is bigger than it needs to: why did you inline the function instead of living in on its own? Apart from that nitpick I think I understand and agree with your change. If you can undo the inlining and squash all your commits then I'll happily merge this. |
|
@trefis hah! turns out my Python was just shaky. I needed access to Squashing, rebasing, and pushing now. |
9b80dd7 to
bcc3b85
Compare
bcc3b85 to
f1403a0
Compare
|
Thank you! |
The usage of the
enclosing_typescache in the Vim plugin is pretty bugged — fixes #732, #770.This is my first PR, so I intentionally went a bit overboard with explanatory comments; I also tried to match the code-style while moving things around.
I won't be offended at all if you have any feedback on how you want this cleaned up — feel free to throw any requirements at me if you want this massaged!
<3