stiegi

stiegi

I would like to have your opinions about a very simple example, because I worked with imperative languages so far only, and I would like to get the mindset of declarative programming.

So i have a function that is called parse_index/1. During runtime we don’t know if we receive an integer or a string as argument, but if it is a string, we want to convert it to a number.
I wrote it like this:

  def parse_index(index) do
    is_number(index)
    |> case do
      true -> index
      false -> Integer.parse(index)
    end
    |> case do
      {number, _} -> number
      number -> number
    end
  end

These are a lot of lines for a pretty simple task, and I was wondering: how small and elegant can you rewrite that by taking advantage of more language features.
It’s really just to learn ‘how to think’ about problems why I ask that, because it kind of feels like I force the imperative way on Elixir when I write it like that…

Thanks!

Showing Posts 1 to 6

kokolegorille

kokolegorille

Hello and welcome,

You could pattern match on function header…

like this

def parse_index(string) when is_binary(string) do
...
end
def parse_index(number), do: number
LostKobrakai

LostKobrakai

I generally tend to use ecto wherever data enters the system and converting it to a known format/type. E.g. using schemaless changesets:

def parse_something_with_an_index(data) do
  {%{index: nil}, %{index: :integer}}
  |> Ecto.Changeset.cast(data, [:index])
  |> Ecto.Changeset.validate_required([:index])
  |> …
end

changeset = parse_something_with_an_index(input)
case Ecto.Changeset.apply_action(changeset, :validate) do
  {:ok, data} -> # correct data
  {:error, changeset} -> # some errors
end

After that you can go on and do whatever you need to do with the data knowing it’s in the format type you expect it to be in.

stiegi

stiegi OP

In that case I would have:

  def parse_index(string) when is_binary(string) do
    Integer.parse(string)
    |> case do
      {number, _} -> number
      :error -> 0
    end
  end

  def parse_index(number), do: number

Then I would have something like this, where I return 0 in case I get a string that cannot be converted. Still wondering if I could / should get rid of the case after the pipe though

stiegi

stiegi OP

Interesting, I really need to take a closer look at Ecto. Thanks for the hint!

kokolegorille

kokolegorille

Pipe is nice, but too much is ugly :slight_smile:

  def parse_index(string) when is_binary(string) do
    case Integer.parse(string) do
      {number, _} -> number
      :error -> 0
    end
  end

… and if You really wanted to, You should have started with

def parse_index(string) when is_binary(string) do
    string
    |> Integer.parse()
    |> case do
      {number, _} -> number
      :error -> 0
    end
  end
stiegi

stiegi OP

I see, thanks! Prefer without pipes here too

— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
kpanic
Hi everyone, I am toying with the idea of building a “match maker” for giving personal help to people that wants to start coding. I sta...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
asweet-confluent
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
mhanberg
Hi everyone! The first release candidate for the Expert language server project is now available! We’ve published a press release detai...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New

Latest on Elixir Forum

Elixir Forum

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews