为何Elixir中Struct定义需使用Keyword Lists而非Map？

Great question! I totally get the confusion—when I first started with Elixir, I tried passing a map to defstruct too and was caught off guard by the error message. Let’s break down the reasons behind this design choice:

• Field order matters
  Unlike maps (which are unordered collections), keyword lists preserve the order of entries. Elixir structs rely on this order for several key behaviors:

  • When you convert a struct to a tuple with Tuple.from_struct/1, the fields appear in the exact order you defined them. This is critical for interoperability with Erlang systems (which use ordered records) and certain serialization workflows.
  • Pattern matching on structs can behave more predictably when field order is consistent, especially in complex codebases.

• Consistency with Elixir's idioms
  Keyword lists are the standard way to pass named options with defaults across Elixir’s core APIs. Think of GenServer.start_link/3 options, use macro parameters, or even IO.puts/2 flags—all use keyword lists. Using the same pattern for defstruct keeps the language’s syntax intuitive and avoids forcing developers to switch mental models between different constructs.

• Avoiding ambiguity
  If defstruct accepted maps, there could be confusion between defining struct fields and passing an initial value. By using keyword lists, Elixir makes it explicitly clear that you’re defining the struct’s schema (field names + default values) rather than setting an initial state.

As a side note, you can even omit the square brackets for brevity—Elixir treats comma-separated key-value pairs as a keyword list automatically:

defmodule User do
  defstruct name: "John", age: 27
end

内容的提问来源于stack exchange，提问作者BlueGene