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 Float conversion or division / multiplications? It seems that :erlang.float is not really used as its not typed(?) and the convention is, to use the Elixir mappings for Erlang stuff.
Claude gave me value / 1 which at first, seemed weird. Since there is no Integer.to_float i would like to hear your opinions on which you prefer and why.
Trending in Questions
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
Hello,
I’m trying to build a basic Phoenix web-app, and I’d like to use Tailwind.
However, when I launch mix phx.server, I get an error...
New
I really like the adapter patterns that ecto, nebulex, waffle, etc. use and would love find something similar for a key management servic...
New
Hello folks!
So at work, we are seeing some situations where we have to define some “fixed” strings that are used across the codebase in...
New
I’m working on a small exercise involving update_in/3, and I came up with this solution:
data = %{
name: "Periodic Table",
category:...
New
I’ve got trouble wrapping my head around the order in which functions are called in this snippet (from Phoenix’s authentication):
toke...
New
Is there any way to avoid the Hologram compiler running when using iex? It seems like the front-end code could potentially be disregarded...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #ai
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming










Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
LostKobrakai
I’d start by asking what reason you have to convert an integer to a float. Then I’d look at how performant this needs to be (hot path or not) and then I’d wonder if it’s worth comparing performance between a bif/nif
float/1vs doing a random calculation likex/1orx*1.0. I’d guess all of them are fast, but no matter what, one will be the fastest. From a readability standpointfloat/1will convey the cleanest that all you do there is convert integer to float.velrest
Thanks for your answer. For instance, we have a Ash calculation which defines
type: :floatand we get values as float as strings and integers. Therefore we need to convert int to float. Im not really worried about performance as this is not hot path but more what the community uses so our code is in line with best practices.karlosmid
Hi, if you plan to do arithmetic with this float better option is to use Decimal, as Decimal handles precision for those operations.
Decimal.new(42)velrest
Okay, since there doesn’t seem too much opinion on this, is maybe my setup flawed since i would expect that people do this regularly?
I have a Ash calculation which has
:floatas return type:calculate :dossier_center_coordinates_x, :float, {SomeCalcThatNeedsToReturnFloat, axis: :x}and in that Calculation i have these functions to match the return type.
Should this be done differently since people don’t seem to have this use case? In my case the calculation should return
:floatbut since its a Module Calculation i don’t think this is enforced anywhere outside of the module.LostKobrakai
Ash uses ecto under the hood so you can simply reuse ectos casting logic:
Ash also seems to wrap this in
Ash.Type.cast_input/3.