Leandro Ostera

@roddyyaga did this fix it for you?

As per @anmonteiro's suggestion we should try using `(include_subdirs qualified)` at the `riot/runtime` level to just ship a single library for the whole runtime.

Hi @alexeyshch! thanks for opening the issue ✨ do you have a use-case for this that can't be solved with some local mutable state in a process?

Hi @FayCarsons! That sounds great :D assigning it to you. Thanks for reaching out! ✨

Here's an example from minttea: https://github.com/leostera/minttea/blob/4f9938c212230898360d009d60689787e51a632f/examples/stopwatch/main.ml#L15-L16 The gist is that a `Ref` is _unique reference_ across the entire execution of your program. No two calls to `Ref.make ()` will ever...

Hmm, off the top of my head we could spin up a blocking process to run some function (eg. count up to max int in a hot loop), and set...

+1 to not relying on the functorized capabilities interface. This gets in the way of using Riot in a unikernel. I'd rather see a configuration (or even runtime) flag for...

Hi @dhikshith12 eventually we could support it, yes :) at this stage, PRs are welcome for work like this since I have [plenty on my plate](https://leostera.notion.site/Riot-Roadmap-9e9796034cc44c9dbb4d13688c38e516).

Hi @jonahbeckford! Thanks for opening the issue ✨ We can loosen the restriction down to OCaml LTS (4.14.2 I think?). Re: the other things, I think these are reasonable feature...

Interesting! Thanks for sharing :) > I am fine with a new version of dkml-c-probe that also emits Rust `target_os`, `target_arch` and `target_family` values ... it is extensible and always...