my_dep VS purerl

diff --git a/mix.exs b/mix.exs index 6ba9745..657162c 100644 --- a/mix.exs +++ b/mix.exs @@ -7,7 +7,9 @@ defmodule PurerlUpAndRunning.MixProject do version: "0.1.0", elixir: "~> 1.14", start_permanent: Mix.env() == :prod, - deps: deps() + deps: deps(), + compilers: [:purerl] ++ Mix.compilers(), + erlc_paths: ["output"] ] end @@ -21,6 +23,7 @@ defmodule PurerlUpAndRunning.MixProject do # Run "mix help deps" to learn about dependencies. defp deps do [ + {:purerlex, "~> 0.4.2"} # {:dep_from_hexpm, "~> 0.3.0"}, # {:dep_from_git, git: "https://github.com/elixir-lang/my_dep.git", tag: "0.1.0"} ]

{:ok, %{ body: "defmodule S3Example.MixProject do\n use Mix.Project\n\n def project do\n [\n app: :s3_example,\n version: \"0.1.0\",\n elixir: \"~> 1.11\",\n start_permanent: Mix.env() == :prod,\n deps: deps()\n ]\n end\n\n # Run \"mix help compile.app\" to learn about applications.\n def application do\n [\n extra_applications: [:logger]\n ]\n end\n\n # Run \"mix help deps\" to learn about dependencies.\n defp deps do\n [\n {:ex_aws, \"~> 2.1\"},\n {:ex_aws_s3, \"~> 2.1\"},\n {:hackney, \"~> 1.9\"},\n {:jason, \"~> 1.2\"},\n {:sweet_xml, \"~> 0.6\"}\n # {:dep_from_hexpm, \"~> 0.3.0\"},\n # {:dep_from_git, git: \"https://github.com/elixir-lang/my_dep.git\", tag: \"0.1.0\"}\n ]\n end\nend\n", headers: [ {"Accept-Ranges", "bytes"}, {"Content-Length", "717"}, {"Content-Security-Policy", "block-all-mixed-content"}, {"Content-Type", "application/octet-stream"}, {"ETag", "\"5ca9425fced3f0bc1670a8f1fccbe29d-1\""}, {"Last-Modified", "Mon, 01 Mar 2021 15:12:06 GMT"}, {"Server", "MinIO"}, {"Vary", "Origin"}, {"X-Amz-Request-Id", "166840A6DA0B6B08"}, {"X-Xss-Protection", "1; mode=block"}, {"Date", "Mon, 01 Mar 2021 15:12:31 GMT"} ], status_code: 200 }}

I will put in a good word for PureScript for the beam with `purerl`. It's my go-to for writing BEAM code nowadays. Notably PureScript tooling including LSP, package management, etc., just works, so you are able to just get to work in internalizing the way OTP and other Erlangy things are expressed in a statically typed, pure language.

https://github.com/purerl/purerl & https://purerl-cookbook.readthedocs.io/ for more information. Join the PureScript discord and the #purerl channel if you want help.

purerl is a compiler for turning PureScript code into Erlang code, so that you're able to write BEAM (the Erlang virtual machine) applications using it.

You've been able to write PureScript that compiles to Erlang and has perfect interop for years, via `purerl`[0]. Using it with Elixir is as simple as adding `purerlex` as a compiler and having your PureScript code automatically compile when `mix` compiles things, and off you go.

In terms of the typing itself, it's exactly what you get in all of PureScript, strict static typing with no `any` or the like. Using `Pinto`, the de facto OTP layer in PureScript your processes are typed, i.e. their `info` messages & state are typed, which means that they are all much more like strongly typed state machines than anything else.

You can see an example of a basic `gen_server` here:

https://pastebin.com/UTEfz7Wg

The differences aren't very big in terms of what you'd expect to be doing. One small thing to note is that the `GenServer.call` expects a closure to be passed instead of having the split between `gen_server:call` & `handle_call`, removing the need for synchronizing two places for your messages being sent and handled.

0 - https://github.com/purerl/purerl