Yorick Peterse
Yorick Peterse
The socket API uses guard types when setting deadlines, and when the guard is dropped the deadline is cleared. The idea behind this is to prevent lingering deadlines. In practise...
During the work on https://gitlab.com/inko-lang/inko/-/merge_requests/120, Inko briefly supported closures that could be called at most once, using the syntax `fn once { ... }`. This was later removed as I...
### Description Expressions such as `x.y := z` should be allowed, provided that `y` is a field and not a method. Currently this is only possible using the syntax `@y...
### Please describe the bug Commit 137304d1cdf6db7d04350fe5675d540fc5543618 introduced support for incremental compilation of LLVM modules/object files. While working on porting my personal website's static site generator over to one written...
### Please describe the bug When using channels, the compiler incorrectly allows types that aren't sendable, both in `async` methods and `Channel.send`. For example, we incorrectly allow this: ```inko class...
### Description The current approach to distributing work is to use a channel, then use e.g. an `enum` as the message, and have a bunch of processes with a `run`...
Inko's sockets are just regular sockets, without any built-in support for TLS (as in SSL/TLS, not thread-local storage). Combine that with the lack of built-in support for various ciphers/cryptographic functions,...
We used to have our own network polling code using epoll/kqueue/etc. While this was simple enough, it was replaced with the polling crate in bf39dbc480ae04ed3949a89e599e5a0f1ea4dd17. Since then maintenance of polling...
Using musl would allow Inko executables to not depend on glibc, making them more portable. Alpine Linux in turn is commonly used in CI environments. Support for Alpine Linux is...
### Please describe the bug When compiling certain pattern match expressions, the compiler incorrectly flags certain cases as unreachable, even though they are in fact reachable. In addition, it seems...