Update CHANGELOG

Author: José Valim

CHANGELOG.md

@@ -1,6 +1,7 @@
 # v0.12.3-dev
 
 * Enhancements
+  * [Kernel] Warnings now are explicitly tagged with "warning:" in messages
   * [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`
@@ -14,10 +15,12 @@
   * [Process] Ensure monitoring functions are inlined by the compiler
 
 * Deprecations
+  * [IEx] The helper `m/0` has been deprecated. The goal is to group all runtime statistic related helpers into a single module
   * [Kernel] `binary_to_term/1`, `binary_to_term/2`, `term_to_binary/1` and `term_to_binary/2` are deprecated in favor of their counterparts in the `:erlang` module
   * [Kernel] `//` for default arguments is deprecated in favor of `\\`. This is a soft deprecation, no warnings will be emitted for it in this release
-  * [Kernel] Deprecate `@behavior` in favor of `@behaviour`
-  * [Record] Deprecate `to_keywords`, `getter` and `list getter` functionalities in `defrecordp`
+  * [Kernel] Deprecated `@behavior` in favor of `@behaviour`
+  * [Record] `to_keywords`, `getter` and `list getter` functionalities in `defrecordp` are deprecated
+  * [Record] `Record.import/2` is deprecated
 
 * Backwards incompatible changes
   * [Dict] Implementations of `equal?/2` and `merge/2` in `HashDict` and `ListDict` are no longer polymorphic. To get polymorphism, use the functions in `Dict` instead

lib/elixir/lib/record.ex

@@ -84,41 +84,9 @@ defmodule Record do
 
       defrecord User, name: "José", age: 25
 
-  Notice that, unlike `defrecordp`, `defrecord` expects an
-  alias as the first argument. This is because `defrecord` is going
-  to create a module named `User` with all the relevant metadata.
-  This module can then be imported and we can manipulate the user
-  as with `defrecordp`:
-
-      Record.import User, as: :user
-      user()        #=> User[name: "José", age: 25]
-      user(age: 26) #=> User[name: "José", age: 26]
-
-  Notice that now since the record definition is accessible, Elixir
-  shows the record nicely formatted, no longer as a simple tuple. We
-  can get the raw formatting by passing `records: false` to `inspect`:
-
-      inspect user(), records: false
-      { User, "José", 25 }
-
-  Since working with external records is common, Elixir allows
-  developers to skip importing the record altogether in favor
-  of a `Module[args]` syntax:
-
-      # Skipping a field uses its default value
       User[]        #=> User[name: "José", age: 25]
       User[age: 26] #=> User[name: "José", age: 26]
 
-  The macro name is replaced by the module name and the parentheses
-  are replaced by brackets. When this syntax is used, there is no
-  need to import the record.
-
-  Before we sum up the differences between `defrecord` and
-  `defrecordp`, there is one last functionality introduced by
-  `defrecord` that we need to discuss.
-
-  ## Runtime access
-
   All the functionality discussed above happens at compilation time.
   This means that both `user(age: 26)` and `User[age: 26]` are expanded
   into a tuple at compile time.
@@ -207,22 +175,7 @@ defmodule Record do
     Record.Extractor.retrieve(name, opts)
   end
 
-  @doc """
-  Import a public record definition as a set of private macros.
-
-  Macros defined as in `Kernel.defrecordp/3`. This is useful when one
-  desires to manipulate a record via a set of macros instead
-  of the regular access syntax.
-
-  ## Example
-
-      defmodule Test do
-        Record.import File.Stat, as: :file_stat
-
-        def size(file_stat(size: size)), do: size
-      end
-
-  """
+  @doc false
   defmacro import(module, as: name) do
     IO.write :stderr, "Record.import/2 is deprecated and it will be removed in the following releases\n#{Exception.format_stacktrace}"