Marcial Gaißert
Marcial Gaißert
There are currently no tests for the `exception` part of the stdlib. (As noticed in #479).
Based on #622. This adds: - Some (minimal) features in the effekt stdlib and the subset of #527 that it depends on - A simple Scanner library (lexing string literals...
Fixes #569. This basically applies this suggestion: https://github.com/effekt-lang/effekt/issues/569#issuecomment-2326363108 but generates a warning instead of an error. We do not seem to use this anywhere.
For writing examples, I wanted to have some standard mutable data structures, currently: - dynamic/resizable arrays - min-heap (=> priority queue) - union-find on integers They all still need more...
This fixes the things noted in #531 (mostly a draft PR so I don't forget): - [x] Double-check whether we need to parenthesize objects or literals in certain places. -...
In general, we need to rethink / redesign the "object-system" anyways. Some aspects are: - [ ] Mutual recursive objects - [x] #274 (globally) - [ ] #600 (locally?) -...
Assume we defined: ``` interface Ping { def ping(): Unit } interface Pong { def pong(): Unit } ``` Then, the following top-level definition is accepted by Effekt (albeit not...
In the following example, the captures are annotated as indicated in the comments: ``` interface Bar { def bar(): Unit } interface Foo { def foo(){b: Bar}: Unit } //...
The following program gives the annotated error: ```effekt interface Done { def done(): Nothing } def main() = { try { do done() } with Done { def done() =...
The following program compiles without typer errors: ```effekt interface Foo { def foo(): Unit } def bar(): Bool / Foo = { do foo() false } def fooo() = {...