angelmz

angelmz

Golang to Elixir code conversion

I’m trying to translate following Go code into Elixir. I’ve also included my own attempt.

package main

import "fmt"

const spanish = "Spanish"
const french = "French"
const englishHelloPrefix = "Hello, "
const spanishHelloPrefix = "Hola, "
const frenchHelloPrefix = "Bonjour, "

// Hello returns a personalised greeting in a given language.
func Hello(name string, language string) string {
	if name == "" {
		name = "World"
	}

	return greetingPrefix(language) + name
}

func greetingPrefix(language string) (prefix string) {
	switch language {
	case french:
		prefix = frenchHelloPrefix
	case spanish:
		prefix = spanishHelloPrefix
	default:
		prefix = englishHelloPrefix
	}
	return
}

func main() {
	fmt.Println(Hello("world", ""))
}

Below I have my attempt at converting it to Elixir. I just want to make sure it’s the “Elixir way” of doing things. What would you all have done differently?

defmodule Hello do
  @english_hello_prefix "Hello, "
  @spanish_hello_prefix "Hola, "
  @french_hello_prefix "Bonjour, "

  # Returns a personalised greeting in a given language.
  def hello(name, language) do
    name = if name == "" do
      "World"
    else
      name
    end
    greeting_prefix(language) <> name
  end

  def greeting_prefix(language) do
    case language do
      "french" -> @french_hello_prefix
      "spanish" -> @spanish_hello_prefix
      _ -> @english_hello_prefix
    end
  end
end

IO.puts Hello.hello("world", "")

Marked As Solved

al2o3cr

al2o3cr

None of the below are “rules”, but some thoughts:

  • putting single-use constants in a module attribute generates identical bytecode to putting them at the point-of-use and only obscures the function where they are used (especially if the attributes are kept at the top of the file while the use site is many lines below). Here’s an alternative greeting_prefix:
def greeting_prefix(language) do
  case language do
    "french" -> "Bonjour, "
    "spanish" -> "Hola, "
     _ -> "Hello, "
  end
end
  • another common style of writing a function with a single simple (no computation in the case ... do) case statement as the body is with pattern-matching like in @D4no0’s version

  • IMO it can be clearer to keep the parts of a function at the same “level of detail”; in this case the name computation and the greeting_prefix computation are both used in hello but the name part has the control structure exposed. Consider making the function more symmetric:

def hello(name, language) do
  greeting_prefix(language) <> name_with_default(name)
end

defp name_with_default(""), do: "World"
defp name_with_default(name), do: name
  • finally, if you find yourself regularly writing case statements against strings, consider making the possible values more explicit by converting to known atoms at a boundary. For instance, you might change the caller of hello to instead pass one of :english, :french, or :spanish and then match exhaustively:
def greeting_prefix(language) do
  case language do
    :french -> "Bonjour, "
    :spanish -> "Hola, "
    :english -> "Hello, "
  end
end

Also Liked

D4no0

D4no0

Your solution is perfectly viable with the exception if name == "" do statement, since elixir is dynamically typed. If you want to check for empty string, you have to ensure that the parameter is string, you can use a guard for this:

def hello(name, language) when is_binary(name) do
    name = if name == "" do
      "World"
    else
      name
    end
    greeting_prefix(language) <> name
  end

As for a different approach, you could do the same with:

defmodule Hello do
  @english_hello_prefix "Hello, "
  @spanish_hello_prefix "Hola, "
  @french_hello_prefix "Bonjour, "

  def greeting_prefix("french"), do: @french_hello_prefix
  def greeting_prefix("spanish"), do: @spanish_hello_prefix
  def greeitng_prefix(_unknown), do: @english_hello_prefix

  def hello(name, language) when byte_size(name) > 0, do: greeting_prefix(language) <> name
  def hello(name, language), do: greeting_prefix(language) <> "World"
end

Where Next?

Popular in Questions Top

rms.mrcs
Hi, I need to transform a list of numbers into a map where the keys are the indexes and the values are the original values of the list. ...
New
electic
Hi, I am new to Elixir. I am trying to use the DateTime component to insert a date into MySQL however the there seems to be no way to fo...
New
minhajuddin
I have seen a lot of code which picks the first element from a list using Enum.at(0) instead of List.first. Is there a reason why people ...
New
Brian
What is the proper way to load a module from a file in to IEX? In the python world, doing something like this pretty standard: from ....
New
openscript
Hello! Sorry for this astonishing simple question, but I’m really stuck. I try to set up the intellij-elixir plugin, but I don’t know ho...
New
Fl4m3Ph03n1x
About me? ( if you have nothing better to do than reading about some random guy in the internet :stuck_out_tongue: ) Hello all, this is ...
New
WestKeys
Currently suffering from paralysis by [HTTP client] analysis. This is rather unusual in Elixirland as there tends to be consensus on the ...
New

Other popular topics Top

ashish173
I am using Ecto timestamps with postgres, I can see the timestamps() use the :naive_dateime but for my use case I wanted to store the ti...
New
sen
Hi All, I set a environment variables in dev.exs , like below code. when i start server, how can i set the ${enable} value? thanks. d...
New
shijith.k
I am trying to start a new phoenix project with elixir 1.9, but mix phx.new does not work. It says that ** (Mix) The task "phx.new" could...
New
msaraiva
Surface is an experimental library built on top of Phoenix LiveView and its new LiveComponent API that aims to provide a more declarative...
564 44139 214
New
Patoshizzle
After calling mix ecto.create I get this error: 17:00:32.162 [error] GenServer #PID&lt;0.412.0&gt; terminating ** (Postgrex.Error) FATAL...
New
Harrisonl
We have an ECS cluster with 4 services, where each task joins a single cluster, via discovery ECS discovery service. Currently when I de...
New

We're in Beta

About us Mission Statement