Document runtime representation of Gleam values #3306
Replies: 4 comments 4 replies
-
A potential idea I came up with is to have a link (to where?) that shows a cheat sheet of what everything in Gleam turns into for each target (maybe with some fancy color-coding to make it easy to distinguish the 3 languages at a glance). For example:
Of course it would be formatted differently. |
Beta Was this translation helpful? Give feedback.
-
I would like to write a guide to FFI, though I have not got around to it myself. |
Beta Was this translation helpful? Give feedback.
-
I decided to start writing an FFI guide myself, and it's going well so far. Still early in development. I'm doing this mainly to learn TypeScript/React because that's what all the jobs want :) I'll probably open the source code soon. I'm running it as a GitHub Pages site, and I'll likely use it for blogging in general. |
Beta Was this translation helpful? Give feedback.
-
I found this blog post which seems to do the same thing I was planning to do. My interest in this has waned, so I'd recommend directing people to that post for FFI information. |
Beta Was this translation helpful? Give feedback.
-
Hello! Gleam's tour covers
@external
definitions by showing some JS usage examples creating aDateTime
. While this might already cover the needs of most casual users I think it would be nice if we had an official documentation page somewhere covering more in-depth details about the runtime representation of things and how to write ffi modules.Some ideas for the erlang target:
Some ideas for the JS target:
Nil
is turned intoundefined
(this is one of those things I always get stuck on)I'm not really sure where this could fit (not really sure the tour is a great place for this kind of details) but it would be really valuable to have this officially documented somewhere. What do you think?
Beta Was this translation helpful? Give feedback.
All reactions