named_args alternatives and similar packages

Based on the "Macros" category.
Alternatively, view named_args alternatives based on common mentions on social networks and blogs.

typed_struct

9.1 10.0 named_args VS typed_struct

An Elixir library for defining structs with a type without writing boilerplate code.
OK

8.9 0.0 named_args VS OK

Elegant error/exception handling in Elixir, with result monads.

Clean code begins in your IDE with SonarLint

Up your coding game and discover issues early. SonarLint is a free plugin that helps you find & fix bugs and security issues from the moment you start writing code. Install from your favorite IDE marketplace today.

Promo www.sonarlint.org

pipes

8.3 0.0 named_args VS pipes

Macros for more flexible composition with the Elixir Pipe operator
pathex

7.9 0.0 named_args VS pathex

Fastest tool to access data in Elixir
shorter_maps

7.5 0.0 named_args VS shorter_maps

Elixir ~M sigil for map shorthand. `~M{id, name} ~> %{id: id, name: name}`
expat

7.2 0.0 named_args VS expat

Reusable, composable patterns across Elixir libraries
eventsourced

6.7 0.0 named_args VS eventsourced

Functional domain models with event sourcing in Elixir
ok_jose

6.2 0.0 named_args VS ok_jose

Pipe elixir functions that match ok/error tuples or custom patterns.
crudry

6.0 0.0 named_args VS crudry

Elixir library for DRYing CRUD in Phoenix Contexts and Absinthe Resolvers.
pipe_to

5.7 1.3 named_args VS pipe_to

The enhanced elixir pipe operator which can specify the target position
mdef

5.1 0.0 named_args VS mdef

Easily define multiple function heads in elixir
pattern_tap

5.1 0.0 named_args VS pattern_tap

Macro for tapping into a pattern match while using the pipe operator
happy

4.5 0.0 named_args VS happy

the alchemist's happy path with elixir
pipe_here

4.4 0.0 named_args VS pipe_here

An Elixir macro for easily piping arguments at any position.
pit

3.2 0.0 named_args VS pit

Elixir macro for extracting or transforming values inside a pipe flow.
rulex

2.8 0.0 named_args VS rulex

This tiny library (2 macros only) allows you to define very simple rule handler using Elixir pattern matching.
guardsafe

2.8 0.0 named_args VS guardsafe

Macros expanding into code that can be safely used in guard clauses.
anaphora

2.7 0.0 named_args VS anaphora

The anaphoric macro collection for Elixir
unsafe

2.2 0.0 named_args VS unsafe

Generate unsafe (!) bindings for Elixir functions
apix

1.7 0.0 named_args VS apix

Simple convention and DSL for transformation of elixir functions to an API for later documentation and or validation.
Bang

1.0 0.0 named_args VS Bang

Bang simply adds dynamic bang! functions to your existing module functions with after-callback.
backports

0.6 0.0 named_args VS backports

Ensure backwards compatibility even if newer functions are used
kwfuns

0.6 0.0 named_args VS kwfuns

Functions with syntax for keyword arguments and defaults
lineo

0.5 0.0 named_args VS lineo

parse transform for accurate line numbers
rebind

0.5 0.0 named_args VS rebind

rebind parse transform for erlang

Do you think we are missing an alternative of named_args or a related project?

Add another 'Macros' Package

Popular Comparisons

README

NamedArgs

Inspired by Named Arguments with Elixir

Allows you to use named arguments similar to Ruby's named arguments. For example, in Ruby

def introduction(name: 'Sarah', birthday: "1985-12-30")  
  puts "Hi my name is #{name} and I was born on #{birthday}"
end

However in Elixir, using a default argument ends up dropping the other values.

defmodule Talk do  
  def introduction(opts \\ [name: "Sarah", birthday: "1985-12-30"]) do
    IO.puts "Hi my name is #{opts[:name]} and I was born on #{opts[:birthday]}"
  end
end
# Drops the birthday
Talk.introduction(name: "Joe") # => Hi my name is Joe and I was born on
# Drops the name
Talk.introduction(birthday: "1985-12-30") # => Hi my name is  and I was born on 1985-12-30

With NamedArgs you can instead do the following:

defmodule Talk do
  use NamedArgs
  def introduction(opts \\ [name: "Sarah", birthday: "1985-12-30"]) do
    IO.puts "Hi my name is #{opts[:name]} and I was born on #{opts[:birthday]}"
  end
end
# No params!
Talk.introduction # => Hi my name is Sarah and my birthday is 1985-12-30
# Keeps the birthday
Talk.introduction(name: "Joe") # => Hi my name is Joe and I was born on 1985-12-30
# Keeps the name
Talk.introduction(birthday: "1986-01-01") # => Hi my name is Sarah and I was born on 1986-01-01
# Order does not matter!
Talk.introduction(birthday: "1986-01-01", name: "Joe") # => Hi my name is Joe and I was born on 1986-01-01

Installation

This package is available in Hex, to install:

Add named_args to your list of dependencies in mix.exs:

    def deps do
      [
        {:named_args, "~> 0.1.0"}
      ]
    end

But it doesn't create a variable with the same name?

Yup, I'm still not sure if thats a desired feature or not. Because it would implicitly create a variable that you may or may not decide to use, it goes against a lot of the philosophies that Elixir follows in regard to explicit coding. And the compiler would warn you about it (and it couldn't be fixed either).

If possible to remove the compiler warning this feature may become more attractive. Please let me know if you have ideas about this!