Marcin Kolny

This is a proposal to expose the functionality directly from posix as oposite to having function per option (we already have placeholders for some of that). Exposing get/setsockopt functions gives...

Extend support for sockets in WASI

4

## Motivation We'd like to be able to build TCP and UDP clients that fully run on WebAssembly runtime. We'd like to be able to build clients like HTTP or...

Registry doesn't have to keep track on the features, as they're only required within a timeline. I'd propose changing `ht_timeline_set_feature()` API to accept destroy callback, i.e.: ```c HT_API void ht_timeline_set_feature(HT_Timeline*...

Currently in TCPListener we use accept() function to accept new connections. However, this function is blocking, and can't be interrupted, therefore test ApplicationShouldNotCrashWhenCreatingListenerFails hangs on mac os. If we rewrite...

We only have unit tests for both - parser and library, but we currently don't have any automation tests for checking if they both work together. Would be great to...

Add feature for measuring duration of arbitrary code

4

Currently we have a scoped tracepoint, which allows us to measure an time of executing the code: ```c { ht_feature_callstack_start_string(timeline, "label"); // some code ht_feature_callstack_start_string_stop(timeline); } ``` Unfortunately we can't...

Currently users have to manually build all the libraries and executables. We should publish installers/rpm/deb packages so they can easily download it and install on their system.

Listeners is quite simple concept, but should be explained in the `Core concepts` section and we should also have a tutorial which shows step by step how to create new...

We already have `cpu_usage` feature for linux-based platforms. Would be nice to implement the interface for windows as well, so the user experience is similar across all supported platforms

We already have CPU usage monitor for Linux, I think it would be useful to have resident memory usage tracker as well.