Replace Ruby stubs with real implementation

Scott Cameron

Created July 29, 2011 00:28

Hi,

I've noticed that when I CTRL-click on a built-in Ruby class it takes me to a stub version of the class that seems to be part of IntelliJ (installed as a plugin). For example, if I click on "alias_method" it takes me to module.rb at \.IntelliJIdea10\config\plugins\ruby\rubystubs\rubystubs18\.

I guess these stubs are used for faster indexing? Is that why it doesn't just use the code from the Ruby interpretor used by the project?

Is there any way to make CTRL-click navigate to the actual implementation instead of the stub without sacrificing performance?

Thanks,
scott

2 comments

Dmitry Jemerov

Created July 29, 2011 01:12

Hello Scott,

A small problem with that idea is the fact that the actual implementation
is written in C.

I've noticed that when I CTRL-click on a built-in Ruby class it takes
me to a stub version of the class that seems to be part of IntelliJ
(installed as a plugin). For example, if I click on "alias_method" it
takes me to module.rb at
\.IntelliJIdea10\config\plugins\ruby\rubystubs\rubystubs18\.

I guess these stubs are used for faster indexing? Is that why it
doesn't just use the code from the Ruby interpretor used by the
project?

Is there any way to make CTRL-click navigate to the actual
implementation instead of the stub without sacrificing performance?

--
Dmitry Jemerov
Development Lead
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"

Scott Cameron

Created July 29, 2011 07:21

Ha, so it is (or in my case, in Java). I didn't realize that the core classes were implemented natively in their entirety but I suppose that makes sense if I think about it for a few seconds. Thanks for pointing me in the right direction.

Cheers,
scott

Please sign in to leave a comment.