You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Two simple modules are attached: f3 and f3lib. Change the filenames to f3.erl and f3lib.erl, and add them to an Erlang project. View the f3 module in Eclipse with Erlide. Place the cursor after the colon in line 8. Press F3, or menu-click and do "Open Declaration". This should cause the f3lib:b/4 function to come into focus. However, it is the f3lib:b/3 function that gets the focus.
The text was updated successfully, but these errors were encountered:
Thanks for reporting that! My guess is that the first function in the file is used, instead of checking the arity. I am now working on a new implementation using the language server protocol, which I hope to be able to release soon (tm), so I'm not sure if it is worth fixing this in the current code. If you think I should, please let me know.
Hi Vlad, I think the coding style with "literal" funs in the argument list of a function call occurs very infrequently in real life. So put your efforts with the new implementation instead, it will be exciting to try out later on.
Two simple modules are attached: f3 and f3lib. Change the filenames to f3.erl and f3lib.erl, and add them to an Erlang project. View the f3 module in Eclipse with Erlide. Place the cursor after the colon in line 8. Press F3, or menu-click and do "Open Declaration". This should cause the f3lib:b/4 function to come into focus. However, it is the f3lib:b/3 function that gets the focus.
The text was updated successfully, but these errors were encountered: