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’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
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
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
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
I recently noticed that Elixir’s Logger defaults its primary log level to :debug when no :logger, :level application configuration is pre...
New
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
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
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
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
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
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
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
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security










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.