Changelog, remove node.to_atom

Author: lpil

CHANGELOG.md

@@ -2,18 +2,28 @@
 
 ## v1.0.0-rc1 - Unreleased
 
-- The `gleam/erlang/os` module has been removed.
-- The `gleam/erlang` module has been removed.
-- The `gleam/erlang/reference` module has been created with the `Reference`
-  type, and the `new` function.
+- In the `gleam/erlang/process` module:
+  - The `Name` type has been introduced. This type is used to give processes
+    names, making it easier to pass references around your application, and to
+    have a new process take over a role from a previous one that has crashed.
+- In the `gleam/erlang/node` module:
+  - The `send` function now sends messages in the same format as the `send`
+    process from the `gleam/erlang/process` module.
+  - The `send` function now accepts a `Name` rather than an `Atom`.
+  - The `to_atom` function has been removed.
+- The `gleam/erlang/reference` module has been created with:
+  - The `Reference` type.
+  - The `new` function.
+- The `gleam/erlang/application` module was created with:
+  - The `priv_directory` function, formerly of the `gleam/erlang` module.
+  - The `StartType` type.
 - In the `gleam/erlang/atom` module:
   - The `AtomNotLoaded` type has been removed.
   - The error type of `from_string` is now `Nil`.
   - The `from_string` function has been renamed to `get`.
   - The `create_from_string` function has been renamed to `create`.
-- The `gleam/erlang/application` module was created with:
-  - The `priv_directory` function, formerly of the `gleam/erlang` module.
-  - The `StartType` type.
+- The `gleam/erlang` module has been removed.
+- The `gleam/erlang/os` module has been removed.
 
 ## v0.34.0 - 2025-02-02
 

src/gleam/erlang/node.gleam

@@ -45,15 +45,11 @@ pub type ConnectError {
 pub fn connect(node: Atom) -> Result(Node, ConnectError)
 
 // TODO: test
-// TODO: document
-// TODO: decide if this should send to just a name of if it should require the
-//       programmer to create a subject first. Current thought is that name is
-//       better because a subject could hold a pid which would already know
-//       what node it is on, so doesn't make as much sense to duplicate that here.
-//       Oh! Wait! Why couldn't a subject specify where the node is?
 /// Send a message to a named process on a given node.
 ///
-/// These messages are untyped, like regular Erlang messages.
+/// This function sends messages in the same format as the send function in the
+/// process module, so messages sent using it can be received as normal using
+/// subjects and selectors.
 ///
 pub fn send(node: Node, name: Name(message), message: message) -> Nil {
   raw_send(#(name, node), #(name, message))
@@ -65,8 +61,3 @@ fn raw_send(
   receiver: #(Name(message), Node),
   message: #(Name(message), message),
 ) -> DoNotLeak
-
-/// Convert a node to the atom of its name.
-///
-@external(erlang, "gleam_erlang_ffi", "identity")
-pub fn to_atom(node: Node) -> Atom

test/gleam/erlang/node_tests.gleam

@@ -17,7 +17,3 @@ pub fn connect_not_alive_test() {
   let name = atom.create("not_found@localhost")
   let assert Error(node.LocalNodeIsNotAlive) = node.connect(name)
 }
-
-pub fn to_atom_test() {
-  let assert "nonode@nohost" = atom.to_string(node.to_atom(node.self()))
-}