doc: Documentation issue in 'kernel/services/data_passing/mailboxes'

[adamtheone]

Describe the bug

In the 'Retrieving Data Later Using a Message Buffer' section, in the 3rd bullet point, there's an extra '.' after k_mbox_data_get() which should not be there, as that's not the end of the sentence.

Environment

• Page: kernel/services/data_passing/mailboxes
• Version: main
• SHA-1: e9987aabbcd46dc583624f10004ddd2b32bbeb3d

[LeviHarrison]

Because of Prometheus's extensive use of the local filesystem, my understanding is that it would prohibitively difficult to compile it to wasm.

[Avey777]

Because of Prometheus's extensive use of the local filesystem, my understanding is that it would prohibitively difficult to compile it to wasm.

Now wasm runtime has wasmrime wasmage wasmer, etc., and support for local files is gradually improving. I think this plan can indeed be considered

[dgl]

WASI on top of WASM is the common system level interface, however it does not currently support mmap -- mmap is pretty crucial for Prometheus (although it could be worked around, but the performance and reliability may suffer, so I'm not sure it would be worth it).

It might be interesting to experiment with compiling parts of Prometheus to WASM before we provided a Docker image, for example running promtool unit tests in a browser could provide some nice benefits.

[roidelapluie]

Prometheus compiles to wasm already but does not work as we do nothing for mmap.