-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Elixir's Kernel defines both to_char_list and to_charlist #4909
Comments
Hmm... Diving in the source, I see that it already is marked as 'TODO: Deprecate in version 1.5', so maybe I spoke too soon and this issue is already kown. Right now it has |
The second version ( We shouldn't show documentation for these functions, so that users will just not see them as available. |
If it's soft-deprected, should that mean, it shouldn't show up when TAB-completing in iex? It currently does show up. That's contrary to |
When i read this issue, i thought of thw same thing michal is mentioning. How did qqwy find out about the function if he hadn't read the source code by then. And IEx came to my mind |
Oh, @michalmuskala is right, it appears in IEx. This appears to be a problem just in |
Should be fixed in 9740544. |
I definitely missed that it was commented D: Thanks @lexmag! |
thank you @lexmag for the fix, it was my fault |
And of everyone who reviewed it, like me. :) it happens! On Saturday, July 2, 2016, Eksperimental notifications@github.com wrote:
José Valim |
@josevalim I think we should backport this to 1.3.x |
Guys, you are awesome 😍 |
Now it's best to use `to_charlist/1` since `to_char_list/1` is being deprecated (see elixir-lang/elixir#4909).
Now it's best to use `to_charlist/1` since `to_char_list/1` is being deprecated (see elixir-lang/elixir#4909).
Current behavior
Elixir's Kernel defines the macro
to_charlist/1
as well asto_char_list/1
. The first version includes documentation, the second version does not.Expected behavior
I am not sure if there is a reason for the second version (
to_char_list/1
) to exist.The text was updated successfully, but these errors were encountered: