From c2dcbe0f25a3e8bd60a4ccf377bbdd47f4794871 Mon Sep 17 00:00:00 2001
From: Louis Pilfold <louis@lpil.uk>
Date: Tue, 26 Mar 2024 13:57:31 +0000
Subject: Document opaque types

Closes https://github.com/gleam-lang/language-tour/issues/63
---
 .../lesson06_multi_target_externals/code.gleam     | 11 -----------
 .../lesson06_multi_target_externals/en.html        | 22 ----------------------
 2 files changed, 33 deletions(-)
 delete mode 100644 src/content/chapter5_advanced_features/lesson06_multi_target_externals/code.gleam
 delete mode 100644 src/content/chapter5_advanced_features/lesson06_multi_target_externals/en.html

(limited to 'src/content/chapter5_advanced_features/lesson06_multi_target_externals')

diff --git a/src/content/chapter5_advanced_features/lesson06_multi_target_externals/code.gleam b/src/content/chapter5_advanced_features/lesson06_multi_target_externals/code.gleam
deleted file mode 100644
index b62a735..0000000
--- a/src/content/chapter5_advanced_features/lesson06_multi_target_externals/code.gleam
+++ /dev/null
@@ -1,11 +0,0 @@
-import gleam/io
-
-pub type DateTime
-
-@external(erlang, "calendar", "local_time")
-@external(javascript, "./my_package_ffi.mjs", "now")
-pub fn now() -> DateTime
-
-pub fn main() {
-  io.debug(now())
-}
diff --git a/src/content/chapter5_advanced_features/lesson06_multi_target_externals/en.html b/src/content/chapter5_advanced_features/lesson06_multi_target_externals/en.html
deleted file mode 100644
index 6e02d36..0000000
--- a/src/content/chapter5_advanced_features/lesson06_multi_target_externals/en.html
+++ /dev/null
@@ -1,22 +0,0 @@
-<p>
-  Multiple external implementations can be specified for the same function,
-  enabling the function to work on both Erlang and JavaScript.
-</p>
-<p>
-  If a function doesn't have an implementation for the currently compiled-for
-  target then the compiler will return an error.
-</p>
-<p>
-  You should try to implement functions for all targets, but this isn't always
-  possible due to incompatibilities in how IO and concurreny works in Erlang and
-  JavaScript. With Erlang concurrent IO is handled transparently by the runtime,
-  while in JavaScript concurrent IO requires the use of promises or callbacks.
-  If your code uses the Erlang style it is typically not possible to implement
-  in JavaScript, while if callbacks are used then it won't be compatible with
-  most Gleam and Erlang code as it forces any code that calls the function to
-  also use callbacks.
-</p>
-<p>
-  Libraries that make use of concurrent IO will typically have to decide whether
-  they support Erlang or JavaScript, and document this in their README.
-</p>
-- 
cgit v1.2.3