Lexer's valid_required? can now be private

Author: José Valim

CHANGELOG.md

@@ -4,8 +4,7 @@
   * [Kernel] Explicit functions inlined by the compiler, including operators. This means that `Kernel.+/2` will now expand to `:erlang.+/2` and so on
   * [Mix] Do not fail if a Mix dependency relies on an outdated Elixir version
   * [Process] Add `Process.send/2` and `Process.send_after/3`
-  * [Version] Add `Version.compare/2`
-  * [Version] Add `Version.valid_requirement?/1`
+  * [Version] Add `Version.compare/2` and `Version.valid_requirement?/1`
 
 * Bug fixes
   * [Atom] Inspect `:...` and `:foo@bar` without quoting

lib/elixir/lib/version.ex

@@ -360,7 +360,7 @@ defmodule Version do
       end
     end
 
-    @doc false
+    @spec parse_pre(String.t) :: [String.t | integer]
     def parse_pre(pre) do
       String.split(pre, ".") |> Enum.map fn piece ->
         if Regex.match?(%r/^(0|[1-9][0-9]*)$/, piece) do
@@ -371,14 +371,8 @@ defmodule Version do
       end
     end
 
-    @spec valid_requirement?(list) :: boolean
-    def valid_requirement?([]) do
-      false
-    end
-
-    def valid_requirement?([a | next]) do
-      valid_requirement?(a, next)
-    end
+    defp valid_requirement?([]), do: false
+    defp valid_requirement?([a | next]), do: valid_requirement?(a, next)
 
     # it must finish with a version
     defp valid_requirement?(a, []) when is_binary(a) do