2 ms·
Looks great, thanks for sharing! I just noticed you committed your .beam files and the _build directory. I think that's a bit unusual. If you don't use specif
by rdtsc 1y ago
Looks great, thanks for sharing!
I just noticed you committed your .beam files and the _build directory. I think that's a bit unusual.
If you don't use specific features of jsx and can restrict compatibility to more recent versions of Erlang/OTP (27+) you might be able to use the built-in json module https://erlang.org/documentation/doc-15.0-rc3/lib/stdlib-6.0/doc/html/json.html https://erlang.org/documentation/doc-15.0-rc3/lib/stdlib-6.0...
- arthurcolle 1y agoDo you have a good example of a rebar3 application / umbrella app that would be good to copy in terms of structure? It has been a minute since I last touched erlang so I haven't really set up a proper directory structure myself before. Maybe I should just create a newbranch and try to set it up using Hex or something, not sure Thanks for mentioning this, it seems I did indeed commit a lot of binary executable files Whoopsie
- rdtsc 1y agoAh no worries at all. Thanks for sharing your library! I think a good start could be rebar3's new app output. rebar3 new app myapp That generates a src directory, a rebar.config file and a .gitignore file. The .gitignore would help keep the beams files out of git. If want others to use your project as a library from Erlang and Elixir an app structure is probably better?
- arthurcolle 1y agoYeah, I would prefer to use Erlang here as I am making this a foundational library for a very large distributed system that I am migrating away from Python to probably Erlang + Rust for an AGI self play project I want to be as close to the BEAM VM as possible