gleam
gleam copied to clipboard
⭐️ A friendly language for building type-safe, scalable systems!
Given a module that imports code from another module, and public types (or functions) using that type, e.g. ``` import gleam/otp/node.{Node} import gleam/otp/actor.{StartError} pub type ApplicationStartMode { Normal Takeover(Node) Failover(Node)...
```rust pub type Box(a) { Box(tag: String, value: a) } pub fn insert(box: Box(a), value: b) -> Box(b) { Box(..box, value: value) } ``` We must ensure that if the...
edit: See comments below for current status.
Not really mergable as is, but is a nice PoC and gives us a spot for discussion - We probably want a way to specify runtime (semi-independent of build target)...
Motivated by this error https://github.com/gleam-lang/gleam/issues/1626 We can do it using the `file` command ```sh $ file gleam gleam: Mach-O 64-bit executable x86_64 ```
https://github.com/gleam-lang/gleam/discussions/1619#discussioncomment-2708716 Also related to https://github.com/gleam-lang/gleam/issues/1117 as I think it would be nice to be able to force it to render them on multiples lines.
Some interesting behaviour was discovered from running `gleam publish` in github actions, notably the error that when a prompt for username was given and the process tries to read from...
The additional type information will aid the JIT in producing faster code. https://erlangforums.com/t/will-does-adding-type-based-guards-make-code-faster-with-the-jit/1361/9 It's not yet clear what the right guards to add is. Some research needs to be done.
Heyo, So I was playing around with some of the erlang `file` functions, and I noticed some interesting behaviour when it came to naming my file `file.gleam`. When importing a...
```gleam // ok // not ok ``` This won't catch all errors, because x could evaluate at runtime to a value that isn't a multiple of 8. However catching the...