There’s a common pattern in Elixir libraries where an “implementation module” is used by generic functions provided by the library, and the library provides a use macro that takes care of filling in the correct parameter automatically.

Examples:

• Ecto.Repo uses this technique to pass the name of the module it’s used in to functions in Ecto.Repo.Schema:

https://github.com/elixir-ecto/ecto/blob/a81aba7840afcf53c3408de17b756ec415a866d6/lib/ecto/repo.ex#L267-L269

• Guardian uses this technique both for it’s core functions as well as for a plug; it’s where I got the term “implementation module” from:

https://github.com/ueberauth/guardian/blob/0b7aba1840bf2f8b75bc3a258463a3fba7f325de/lib/guardian.ex#L401-L404

https://github.com/ueberauth/guardian/blob/0b7aba1840bf2f8b75bc3a258463a3fba7f325de/lib/guardian/plug.ex#L80-L81

Is there a name for this pattern? “Specialization”? “Compile-time currying”?