Tim Whiting

By the way, I have a version of the libuv branch, which uses this api, and automatically generated ffi bindings (adapted from dart's `ffigen`). This allows us to write almost...

Yes, I've run into this several times as well.

This is the commit that broke this: https://github.com/koka-lang/koka/commit/bb6c56bdd2a691cdd686bf8065cf8980aa1c59b2 However, reverting the particular change involves a few other commits as well. So it isn't a simple fix.

This would potentially require deleting the original function or modifying the name of the original function. But I agree that it would be more intuitive to users.

Random thought, feel free to reject. What if the macro system generates code into a collapsed block right after the annotation. Then you have both signatures side by side and...

The main problem I see with this approach is that you are creating a method `_example` but have to use it as `Example()` with fewer parameters. Which is what this...

Thinking some more about this I was wondering if reusing the annotation syntax is going to limit macros applicability in these situations, since currently macros always have to have an...

Statement level macros would fix a lot of the limitations I see with the current approach. Glad it's being considered!

Yeah, I'd be happy to start contributing to a `material_zap` or `zap_components` package. As far as design for these components, I'd like to provide some styling options as a theme...

Isn't being able to make sense of code more important than having to deal with resizing windows? Sure, it'd be pretty impossible to make sure every potential piece of code...