When passing Wasm function to the host as a callback, it's passed as an index in the table.
Wasm3 needs to provide an API to call such functions.

It's common when writing scripts that install or configure things to need input from the user (at a minimum, something like 'Press Enter to continue'; at a maximum, to be able to prompt the user for input, with an optional default value, and return that value).

Let's use this issue to design how that would look, and I invite suggestions!

Reexporting a type or value from one module to another should check the visibility of the original item.

This can happen in a few cases:

//- foo.mun
// Illegal, Bar has a smaller scope that this use statement
pub(super) struct Bar;

// Illegal, Bar has a smaller scope than this function
pub fn baz() -> Bar {
}

//- mod.mun
pub use foo::Bar; // Should be illega

Is there a convenient way to format a FileStatus? I am looking for an interactive equivalent of the Unix ls -l, and it seems that I have to write this from scratch.

FWIW, here is my current attempt -- I'm sure it can be improved.

Describe the bug
testLineAgainstWater checks only for water at z-coordinate 0 outside of the -3000 : 3000 coords range. This behaviour was introduced along with multiple other fixes with this PR: multitheftauto/mtasa-blue#568
Some time afterwards, possiblity to change ocean water level outside of bounds was added for setWaterLevel function, thus rendering curr

Affects:

• Installing plugins from Plugin Repository
• Installing plugins using URL Scheme

Current Behavior:

HTTP errors are not handled, user may end-up with a broken "plugin" file, see #59 as example.

Desired Behavior:
Proper Error handling, including:

• checking HTTP error codes
• showing user a dialog if something went wrong
• maybe adding additional checks like tryi

Apart from jbang help and the examples of jbang use given in the readme, it would be great to have:

1. A documentation - Picocli generated ?
2. A cheat sheet usable with https://github.com/cheat/cheat

The second one is very efficient, as you document only the most frequent usages of a command, so you find very quickly the command you need.

Description

Recently the markdown file for the Python directory was reformatted, since then the list hasn't been updated.
Follow the same structure as of the README, update the list alphabetically.

The CMakeLists files of this project is kinda messy, mostly due to my limited understanding of the topic.

So they definitely need to be cleaned up at some point

It'd be very nice to have an auto-formatter for Rune which can take a source-snippet and format it properly.